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 19:58: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: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: symtab/1253: [regression] bad backtrace for '<function called from gdb>'
Date: Sat, 2 Aug 2003 15:52:02 -0400
On Fri, Aug 01, 2003 at 11:32:59PM -0400, Michael Elizabeth Chastain wrote:
> Okay some more clue droppings ...
>
> The problem is localized inside "sleep". If I set a breakpoint
> on "sleep" and then "stepi" through it, gdb has some funky ideas
> of where the stack is.
>
> The code for "sleep" is:
>
> 0x420ae310 <sleep>: push %ebp
> 0x420ae311 <sleep+1>: xor %ecx,%ecx
> 0x420ae313 <sleep+3>: mov %esp,%ebp
The best way to handle this, IMVHO, would be to move Jim B's neat
prologue analysis infrastructure out of s390-tdep.c and into common
code; then it becomes trivial to recognize new instructions as they're
encountered.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer