This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 2 Aug 2003 01:28:00 -0000
- Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
- Reply-to: Daniel Jacobowitz <drow at mvista dot com>
The following reply was made to PR symtab/1253; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@mvista.com>
To: mec@shout.net
Cc: gdb-gnats@sources.redhat.com
Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
Date: Fri, 1 Aug 2003 21:18:48 -0400
On Mon, Jun 23, 2003 at 03:57:53PM -0000, mec@shout.net wrote:
>
> >Number: 1253
> >Category: symtab
> >Synopsis: [regression] bad backtrace for '<function called from gdb>'
> >Confidential: no
> >Severity: critical
> >Priority: medium
> >Responsible: unassigned
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Mon Jun 23 16:08:00 UTC 2003
> >Closed-Date:
> >Last-Modified:
> >Originator: mec@shout.net
> >Release: gdb HEAD 2003-05-30 20:00:00 UTC
> >Organization:
> >Environment:
> target=native
> host=i686-pc-linux-gnu
> osversion=red-hat-8.0
> gdb=HEAD%20030621
> gcc=3.3
> binutils=2.14
> glibc=2.2.93-5-rh
> gformat=dwarf-2
> glevel=2
> >Description:
> gdb loses the fp chain when backtracing through a function called from a hand-function-call. This is a regression from gdb 5.3.
>
> With gdb HEAD%20030409 the call stack is okay:
>
> subroutine
> handler
> <signal handler called>
> nanosleep
> sleep
> have_a_very_merry_interrupt
> <function called from gdb>
> main
Ah, so this also involves sleep().
You're going to have to do some more investigation. This is a symptom
of some difference between your C library and mine, i.e. it works here
using your executables.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer