GDB 4.16 dumps core with egcs-1.0
Raffaele Sena
raff@aromatic.com
Tue Jan 13 15:26:00 GMT 1998
>
> Now I use pgcc-1.0.1 (based on egcs-1.0.1) and the bug still occurs. I
> don't think that pgcc changes the init-code.
>
Again, you should be able to get a working gdb by uncommenting
the following lines in gdb-4.16/gdb/Makefile.in and
rebuilding gdb:
Makefile.in: line 96
# To use your system malloc, uncomment MMALLOC_DISABLE.
#MMALLOC_DISABLE = -DNO_MMALLOC
# To use mmalloc but disable corruption checking, uncomment MMALLOC_CHECK
#MMALLOC_CHECK = -DNO_MMALLOC_CHECK
Maybe you also want to comment out the previous lines, just to
make sure.
Also, I'm still not convinced egcs is responsible for the problem.
Even if it calls malloc in the initial phase, when it's linked
with the mmalloc package, all the standard allocation functions
(malloc, free, calloc, realloc) are redefined to call the
m-functions.
So, you should get the error if you have other packages called
by gdb (shared library ?) that allocate memory then released by
gdb. Again I had the problem when I built gdb-tk, based on
gdb-4.16, where I think some part of the tk library were trying
to release memory allocated by X/11.
Anyway, I'll try to build a standard gdb-4.16 and see what happen.
-- Raffaele
More information about the Gcc-bugs
mailing list