From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1152 invoked by alias); 9 Nov 2005 14:02:22 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 1141 invoked by uid 22791); 9 Nov 2005 14:02:18 -0000 Received: from ns2.suse.de (HELO mx2.suse.de) (195.135.220.15) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 09 Nov 2005 14:02:18 +0000 Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id C556A1D758 for ; Wed, 9 Nov 2005 15:02:15 +0100 (CET) Date: Wed, 09 Nov 2005 14:02:00 -0000 From: Olaf Hering To: Andreas Schwab Cc: gdb@sourceware.org Subject: Re: trouble with gdb backtraces on ppc with gcc4 Message-ID: <20051109140215.GA18309@suse.de> References: <20051109130501.GA16450@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-DOS: I got your 640K Real Mode Right Here Buddy! X-Homeland-Security: You are not supposed to read this line! You are a terrorist! User-Agent: Mutt und vi sind doch schneller als Notes (und GroupWise) X-SW-Source: 2005-11/txt/msg00198.txt.bz2 On Wed, Nov 09, Andreas Schwab wrote: > Olaf Hering 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=, data=, 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=, 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=) 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