aspell-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[aspell] aspell dying during check


From: Sean 'Shaleh' Perry
Subject: [aspell] aspell dying during check
Date: Fri, 08 Dec 2000 13:45:38 -0800 (PST)

When I am spell checking a SGML doc that is fairly technical (this time it is
PAM docs) aspell eventually dies.  I think this has something to do with my
liberal use of 'Ignore all' to get past things like '/etc/passwd'.

The backtrace from gdb is:

Program received signal SIGSEGV, Segmentation fault.
afilter::FilterItrRootClass<_Rope_const_iterator<char, allocator<char> >,
afilter::itr_equal<_Rope_const_iterator<char, allocator<char> > > >::next (
    this=0x8147b28) at ../filter/filter.hh:167
167           else return *ritr;
(gdb) bt
#0  afilter::FilterItrRootClass<_Rope_const_iterator<char, allocator<char> >,
afilter::itr_equal<_Rope_const_iterator<char, allocator<char> > > >::next (
    this=0x8147b28) at ../filter/filter.hh:167
#1  0x400f7d46 in
afilter::RegionSkipItr<afilter::SgmlSkip<afilter::RegionSkipFilterTypes>
>::next () from /usr/lib/libaspell.so.8
#2  0x400ec009 in
afilter::ReplItr<afilter::DualRepl<afilter::CharReplBase<afilter::char2uni>,
afilter::CharReplBase<afilter::uni2char> >, -1, -1>::next ()
   from /usr/lib/libaspell.so.8
#3  0x400f5d3d in
afilter::BlockSkipItr<afilter::UrlSkip<afilter::BlockSkipFilterTypes> >::next
() from /usr/lib/libaspell.so.8
#4  0x4009f07d in aspell::TokenItr::advance () from /usr/lib/libaspell.so.8
#5  0x805e447 in void aspell::check<_Rope_const_iterator<char, allocator<char>
>, afilter::itr_equal<_Rope_const_iterator<char, allocator<char> > >,
aspell::DoNothing> (address@hidden, address@hidden)
    at ../lib/inc/check.hh:170
#6  0x80558f4 in check (interactive=true) at aspell.cc:857
#7  0x804e870 in main (argc=4, argv=0xbffffaa4) at aspell.cc:274
#8  0x401d7c1c in __libc_start_main () from /lib/libc.so.6

the myriad of interators here has my brain in loops.  Wish I could debug it
further.  BTW I also posted this to the sourceforge bug tracker, but thought i
might get a response here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]