Description of Problem: Whenever I run 'aspell -c -H blah.xml' on a Docbook-style document, it does not get to the point of presenting me with options to correct spelling errors. Version-Release number of selected component (if applicable): aspell-0.33.7.1-16 How Reproducible: always Steps to Reproduce: 1. Grab an XML document. One that is publicly available that I know fails is in gnome-devel-docs/tutorials/i18n/C/i18n-guide.xml in the GNOME CVS repository. 2. Run 'aspell -c -H i18n-guide.xml' 3. You will need to ^C the application eventually, since it does nothing. Actual Results: The application appears to just hang, but eventually the disks start grinding away (swapping). Running strace on the process shows that it gets stuck requesting more and more memory (lots of brk(...) system calls one after another). Expected Results: The document above certainly has spelling errors in it, particularly if you use the standard dictionary. So I would expect to see the screen come up that reports misspelt words and gives options for correcting them. Additional Information: (1) Running the same command on the same document on Red Hat 7.3 machines (aspell-0.33.7.1-9) works perfectly. The "corrections screen" comes up after only a couple of seconds. I was previously using aspell a lot on these boxes and never saw the above problem. (2) Running the same command on four different Red Hat 8.0 installations (with different CPU and memory configurations) shows the behaviour in this report. (3) Running the command 'aspell -c i18n-guide.xml' brings up the "corrections screen" almost instantly (just as on Red Hat 7.3), however, since it does not know that this is an SGML-style document, it complains about most of the tags and their attributes being misspelt, so this is not an acceptable workaround.
I am seeing the same behavior. strace shows gobs and gobs of brk() calls whenever I try to run 'aspell' on a .html file.
Similar results here. when I run it in --list mode, it works fine. I'm attaching a sample file. When I name the file emb, it works fine, when I check it as emb.html, I get the same result... infinite loop allocating 4K chunks via break. One interesting thing is that the file doesn't generate any error messages for me in --list mode, so it can't be choking on the 'display errors' section (it also failed when I had mispellings). The wierd thing is that an adb traceback seems to indicate that it's doing this inside of free (!). (gdb) back #0 0x42074a27 in free () from /lib/i686/libc.so.6 #1 0x4015bde3 in operator delete(void*) (ptr=0x0) at ../../../../libstdc++-v3/libsupc++/del_op.cc:39 #2 0x4009a338 in afilter::MapReplReadError::expecting_keyword::~expecting_keyword() () from /usr/lib/libaspell.so.10 #3 0x4009914b in autil::GenericCopyPtr<afilter::MapReplReadError::error, autil::ClonePtr<afilter::MapReplReadError::error>::Parms>::~GenericCopyPtr() () from /usr/lib/libaspell.so.10 (backtrace goes to #14). Dies under Redhat 8.0 seems to work fine under 7.2 and 7.3 for 8.0: [samuel@algh1188y43bi slash]$ rpm -qa | grep -i spell pspell-0.12.2-14 aspell-en-ca-0.33.7.1-16 gnome-spell-0.4.1-4 aspell-0.33.7.1-16 aspell-en-gb-0.33.7.1-16 for 7.3: [samuel@reality samuel]$ rpm -qa | grep -i spell pspell-0.12.2-8 gnome-spell-0.4.1-0.7x aspell-0.33.7.1-9
Created attachment 89188 [details] Reasonably small test case kills aspell as emb.html, but not as emb. In the latter case, it claims no spelling errors. (also dies with spelling errors)
aspell will be upgraded in the next release