Re: [Bug: 21.5-b16] Gnus-induced freed lrecord crash again
Darryl Okahata <darrylo(a)soco.agilent.com> wrote:
Try compiling with plain -g (no optimization), and without all
of
the cpu- and instruction-generation-specific flags. Gcc is legendarily
buggy, and some of the flags that you're using are known to be broken in
some circumstances (e.g., gcc 3.2, don't know about 3.3).
I did that to get a version I could use with valgrind (which nominally
supports only 486 code, but does have partial support for some later
stuff). I got the crash in that situation, too, so we can't blame it on
the gcc flags. Now that I've snagged icc, I'll build and run with that
for awhile. If I get the crash again, then we'll know it's not the
compiler. Thanks for the suggestion!
--
Jerry James
http://www.ittc.ku.edu/~james/