|
From: Chris S. <c.s...@co...> - 2005-01-12 14:52:10
|
On Tue, Jan 11, 2005 at 04:57:40PM -0500, Chris Shoemaker wrote: > On Tue, Jan 11, 2005 at 04:22:39PM -0500, Chris Shoemaker wrote: > > > > Now: perhaps I'm doing something dumb, but is there some way I can > > preserve stack frame info when I attach gdb? > <snip self> > > > > [chris@badger2 test]$ gdb a.out > > GNU gdb Red Hat Linux (6.1post-1.20040607.43rh) > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public License, and you are > > welcome to change it and/or distribute copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show warranty" for details. > > This GDB was configured as "i386-redhat-linux-gnu"...(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". > > After doing a bit more testing, I discovered that changing gdb versions makes a difference. > gdb that came with FC1, gdb-5.3.90-0.20030710.41.i386.rpm, shows stack info. > gdb that came with FC2, gdb-6.0post-0.20040223.19.i386.rpm, DOESN'T. > and neither does the more recent, (6.1post-1.20040607.43rh) > > However, on a debian box, (gdb 6.1-debian), has no problem. I guess I > should find the gdb mailing list, huh? I don't know what's special about gdb 6.1-debian, but a stock gdb 6.3 also fixes this problem. Sorry for the noise. -chris |