Newest gcc memory leak on gdb (heads up, only)
Donn Terry
donnte@microsoft.com
Wed May 29 14:30:00 GMT 2002
Just in case someone else is also looking at this....
Sometime between 5/13 and yesterday (5/28) evening (4:30P Pacific), a
change was made to
either gdb or gcc such that attempting to compile gdb/p-typeprint.c
causes a bad memory leak (at least for me). (After 30 seconds it was at
300M
and finally it grows enough to crash.)
I'm looking at this now to figure out what's going on. If anyone else
is looking into this, please let me know.
Donn
More information about the Gdb
mailing list