> > I wouldn't exactly consider myself a guru, but I had a look, and I can't
> > see anything
> > obviously wrong with the file.  As far as I can tell by means of Mark I
> > Eyeball, it
> > is in compliance with the language.dtd file included in the same
> > directory, and therefore
> > has correct syntax (although a recheck with a proper parser might turn up
> > something that I missed).

Thanks for looking. My apologies for not posting a followup to the question:

I filed a bug report:

http://bugs.trinitydesktop.org/show_bug.cgi?id=1279

In the bug report I identified the problematic line and posted a simple work-around. I don't know the root cause, but I guess a problem parsing the regex.

> Can anyone here try to run kwrite under kcachegrind, open a
> kcrash file, and post the results?  This will help us figure out
> what section of the code kwrite is "stuck" in.
> 
> Here is a quick tutorial:
> valgrind --tool=callgrind kwrite
> <open the kcrash file, wait for it to show up in kwrite,
> then immediately
> close kwrite>
> Then post the generated callgrind.out.<pid> file to
> this list.

I don't know what valgrind is [search...search...search]. Okay, a debugging tool, but I'm still out of my league. :)

Darrell