This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] arm_skip_prologue: recognize "str r(0123), [r11, #-nn]"
- From: Michael Snyder <msnyder at redhat dot com>
- To: Richard dot Earnshaw at arm dot com
- Cc: Michael Snyder <msnyder at cygnus dot com>, gdb-patches at sources dot redhat dot com, cagney at redhat dot com, rearnsha at arm dot com
- Date: Tue, 23 Apr 2002 10:35:31 -0700
- Subject: Re: [RFA] arm_skip_prologue: recognize "str r(0123), [r11, #-nn]"
- Organization: Red Hat, Inc.
- References: <200204230954.KAA01842@cam-mail2.cambridge.arm.com>
Richard Earnshaw wrote:
>
> > >
> > > GCC sometimes generates these stores as discrete instructions.
> > >
> > > 2002-04-22 Michael Snyder <msnyder@redhat.com>
> > >
> > > * arm-tdep.c (arm_skip_prologue): Recognize str r(0123), [r11, #-nn].
> > >
> >
> > Are you sure these should really be considered part of the prologue?
> >
> >
> >
>
> Ok, here's how I think we should consider this.
>
> If a DWARF-encoded sequence would consider these as part of the prologue
> (ie they are described as prologue instructions, then the unwinder should
> consider them similarly. If, however, it considers them as part of the
> function body then the manual unwinder should also do so.
Richard,
This disassembly method is only invoked if there is no dwarf info.
If we do have line numbers etc, we use those by preference.
So when we are disassembling, we cannot rely on hints from the
debug info.
I have confirmed that, when there is debug info,
these instructions are lumped with the prologue.
>
> If the latter is correct, then we should also handle storing into the
> stack so that we can also handle frameless functions.
>
> R.