Re: [AC21.5] segfault during compilation
>>>>"AM" == Alexey Mahotkin
<squadette(a)gmail.com> writes:
AM> Marcus, if our theory is that it is a
memory corruption bug --
AM> when you run valgrind on your machine -- does it say that xemacs
AM> is clean?
Valgrind complains about some Lstream-related invalid reads, but
nothing concerns the new allocator. You'll probably see the same when
you run valgrind on the other system you mentioned where XEmacs works.
--
Marcus