From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.3)
Description of problem:
Probably not a bug, I must have something configured incorrectly, but...
I am having the same symtoms reported in Bug #54391 (which was
resolved last year)
When I spell check any .tex file, I get a core dump and the emacs
process runs away (100% CPU) and have to kill the process.
The interesting part is that if I create a very simple file, say
'test.txt' and spell check (from within emacs) aspell works fine. If I
copy that same file to test.tex and then try to spell check the file I
get the hung process. Finally, copy the file to test.html, aspell
I tried this simple method to identify if there was some characters
within my tex documents that was causing aspell trouble.
The core dumps are attributed to aspell,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.As outlined above - create a file with just four lines of text, save
the file as test.txt; spell check the file (from within emacs) - no
2.Copy the above file to test.tex (at the command line), open in
emacs, try to spell check, I get a core dump (aspell) and then have to
kill the emacs process.
3. Copy the same file to test.html, open in emacs, spell check no
Looks like this is probably an aspell bug on x86_64.
Seems to be ok with rawhide/fc3 test releases afaics.
can't reproduce with my machines; i'm not seeing this on current
x86_64 builds either.