Follow-up Comment #12, bug #30766 (project gnustep):
I'm afraid there's little that those of us without hppa systems (like myself)
can do other than offer a bit of advice.
The fact that very different stacktraces are showing crashes in malloc
suggests that the problem is memory corruption which occurred elsewhere (and
there are probably no real clue to the original cause in the stacktraces).
This suggests that using gdb is unlikely to be helpful initially.
In which case, the only approach which really offers any reasonable prospect
of success would be to check out base from svn trunk on various dates, and see
at what point the test program starts crashing. That will narrow things down
to the code change at which crashing started ... at which point we can examine
the source to see if we can spot anything, and also run under gdb setting
breakpoints at any changed section of code, and stepping through to see what's
going on.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30766>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
