This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: c++/625: gdb loops chewing up all memory on p command
- From: mec at shout dot net
- To: gdb-prs at sources dot redhat dot com, john dot carter at tait dot co dot nz, mec at shout dot net, nobody at sources dot redhat dot com
- Date: 13 Aug 2003 20:16:54 -0000
- Subject: Re: c++/625: gdb loops chewing up all memory on p command
- Reply-to: mec at shout dot net, gdb-prs at sources dot redhat dot com, john dot carter at tait dot co dot nz, mec at shout dot net, nobody at sources dot redhat dot com, gdb-gnats at sources dot redhat dot com
Synopsis: gdb loops chewing up all memory on p command
Responsible-Changed-From-To: unassigned->chastain
Responsible-Changed-By: chastain
Responsible-Changed-When: Wed Aug 13 20:16:54 2003
Responsible-Changed-Why:
I'll look into this.
State-Changed-From-To: open->feedback
State-Changed-By: chastain
State-Changed-When: Wed Aug 13 20:16:54 2003
State-Changed-Why:
I confirmed this with gdb 5.2.1, gcc 3.3.1, binutils 2.14, on native i686-pc-linux-gnu (red hat 8).
gdb 5.2.1 consumes all available memory and then falls over.
gdb 5.3 prints some fields of 'a' and then prints some bogus information.
gdb gdb_6_0-branch works okay -- it prints all the fields of 'a'.
The current CVS version of gdb works fine, too.
Can you try this snapshot and let me know if it fixes the problem for you:
ftp://sources.redhat.com/pub/gdb/snapshots/branch/gdb+dejagnu-5.3.90_20030813.tar.bz2
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=625