Re: Memory corruption errors!?
Adrian Aichner writes:
Mats, I'm not sure, but it looks as if you have note enabled the
new
incremental garbage collector itself.
OK. I though that ">> Using the new GC mark algorithms (KKCC)." was just
that but then
again it might just be the "new GC mark algorithms" which probably is something
completely different.
Try again with
--enable-newgc
Thanks. I might do that but then, if I'm not using the new GC, the problem is more
alarming because it then seems like something old is broken.
Other than that your configuration below looks good for providing
useful call stack information.
Let me try again. I have a stack trace. I just want to know whether it can be useful
when it comes to these "Memory corruption errors".
Yours
--
%% Mats