Re: trouble with gdb backtraces on ppc with gcc4

[Olaf Hering <olh@suse.de>]

 On Wed, Nov 09, Andreas Schwab wrote:

> Olaf Hering <olh@suse.de> writes:
> 
> > the backtraces in gdb 6.3 and also in gdb-mainline are usually broken in
> > openSuSE. How does gdb generate them? I guess gdb needs to deal with the
> > gcc generated debug info.
> 
> When there is one.  In your example there isn't.  The openSuSE gdb has
> been patched to make use of the DWARF unwind information, which works
> quite well if it is present.

seems to work better.

(gdb) bt
#0  0x0ff6467c in __write_nocancel () from /lib/libc.so.6
#1  0x0ff143a4 in _IO_new_file_write (f=0xffea9b8, data=0x40017000, n=13) at fileops.c:1260
#2  0x0ff128c0 in new_do_write (fp=0xffea9b8, data=0x40017000 "i 1351088395\n\n", to_do=13) at fileops.c:514
#3  0x0ff12a78 in _IO_new_do_write (fp=<value optimized out>, data=<value optimized out>, to_do=13) at fileops.c:486
#4  0x0ff13604 in _IO_new_file_overflow (f=0xffea9b8, ch=-1) at fileops.c:865
#5  0x0ff145d4 in _IO_new_file_xsputn (f=0xffea9b8, data=<value optimized out>, n=1) at fileops.c:1340
#6  0x0feeb9a0 in _IO_vfprintf (s=0xffea9b8, format=0x10000914 "i %d\n", ap=0xffffe450) at vfprintf.c:1565
#7  0x24000484 in ?? ()
#8  0x0fef2c40 in printf (format=<value optimized out>) at printf.c:34
#9  0x100004fc in t1 (i=1351088395) at t1.c:4
#10 0x10000488 in main () at main.c:8

> No debug info in /lib/tls/libc.so.6.  Will work fine when debug info
> exists.

Well done. There is none...

-- 
short story of a lazy sysadmin:
 alias appserv=wotan