Re: Memory corruption errors!?
>>>>"ML" == Mats Lidell <matsl(a)xemacs.org>
writes:
ML> Adrian Aichner wrote:
> Mats Lidell <matsl(a)xemacs.org> writes:
>
> Mats, I'm not sure, but it looks as if you have note enabled the new
> incremental garbage collector itself.
>
> Try again with
> --enable-newgc
ML> Using the newgc made the memory problem go way. That made my day
ML> but someone should maybe look out for this and why it occured in
ML> the first place. Maybe all 21.5 users are using the new newgc,
ML> ;-), or have not synced with CVS lately, :-(.
It would be really helpful if you could run valgrind on your broken
build (the one without NEWGC).
Something like
valgrind --db-attach=gdb src/xemacs
or
valgrind --gdb-attach=yes src/xemacs
should do the trick (depends on your valgrind version).
When valgrind complains about the memory corruption, please attach the
debugger and post the backtrace.
Thanks,
--
Marcus