Mine is 3.3.1. Do you think it's worth the trouble to protect 3.3.1
users
from this crash (which is admittedly rare, you'll need to scale a text string to microscopic sizes to get it)?
Can you upgrade to 3.3.2 and try to replicate the bug, so we can rule out factors other than the compiler?
Just upgraded to 3.3.2 - alas, the bug is still there. What else can be done, aside from the "magic fix"?
Here's my g++ -v:
Reading specs from /usr/lib/gcc-lib/i586-mandrake-linux-gnu/3.3.2/specs Configured with: ../configure --prefix=/usr --libdir=/usr/lib --with-slibdir=/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --disable-checking --enable-long-long --enable-__cxa_atexit --enable-languages=c,c++,ada,f77,objc,java,pascal --host=i586-mandrake-linux-gnu --with-system-zlib Thread model: posix gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-3mdk)
_________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=dept/bcomm&pgmarket=en-ca&RU=http%3a%2f%2f...