Backtrace with #-1 frame?

Backtrace with #-1 frame?

[Jon Ringle]

I am having problems doing a backtrace with the latest gdb cvs code. Below is 
a testcase:

Jon

[ringlej@heavymobile testcode]$ cat foo.c
#include <stdio.h>

void foo(int i)
{
        printf("foo(%d)\n", i);
}

void bar(int j)
{
        printf("bar(%d)\n", j);
        foo(j+1);
}

int main(void)
{
        bar(1);
}
[ringlej@heavymobile testcode]$ CFLAGS="-g -O0" make foo
cc -g -O0    foo.c   -o foo
[ringlej@heavymobile testcode]$ ~/gdb-cvs/i686/gdb/gdb foo
GNU gdb 6.3.50.20050329-cvs
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 "i686-pc-linux-gnu"...Using host libthread_db 
library "/lib/tls/libthread_db.so.1".

(gdb) b foo
Breakpoint 1 at 0x8048372: file foo.c, line 5.
(gdb) run
Starting program: /home/ringlej/testcode/foo
Backtrace limit of 50 exceeded
Backtrace limit of 50 exceeded
bar(1)
Backtrace limit of 50 exceeded

Breakpoint 1, foo (i=2) at foo.c:5
5               printf("foo(%d)\n", i);
(gdb) bt
#-1 foo (i=2) at foo.c:5
Backtrace limit of 50 exceeded
(gdb)

Re: Backtrace with #-1 frame?

[Daniel Jacobowitz]

On Tue, Mar 29, 2005 at 03:56:37PM -0500, Jon Ringle wrote:
> I am having problems doing a backtrace with the latest gdb cvs code. Below is 
> a testcase:

This is a bug in the "set backtrace limit" command.  Find where you
have a .gdbinit setting that and disable it to work around the problem;
I haven't investigated the actual bug.

-- 
Daniel Jacobowitz
CodeSourcery, LLC