This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: [PATCH RFA] step-test.exp changes for IA-64
- To: Kevin Buettner <kevinb at cygnus dot com>
- Subject: Re: [PATCH RFA] step-test.exp changes for IA-64
- From: Michael Snyder <msnyder at cygnus dot com>
- Date: Sat, 13 May 2000 07:58:20 -0700
- CC: gdb-patches at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <1000426034223.ZM12414@ocotillo.lan> <1000513063534.ZM23830@ocotillo.lan>
- Reply-To: msnyder at cygnus dot com
Kevin Buettner wrote:
>
> This patch was applied earlier today. At Fernando's request, I added
> some additional comments describing the reason for the different behavior
> on the IA-64.
>
> On Apr 25, 8:42pm, Kevin Buettner wrote:
> > Subject: [PATCH RFA] step-test.exp changes for IA-64
> > I request approval for committing the changes below.
> >
> > On IA-64, when using "finish" to step out of a function, gdb will stop
> > on the line containing the call to the function that you've just
> > stepped out of. The reason for this is that immediately after the
> > call instruction is an instruction which restores the global pointer.
> > Since this is part of the sequence of instructions forming the call,
> > it makes sense that gdb would place you on the line of the call instead
> > of the next executable line after the call.
Such behavior is not all that unusual. It might be good to
generalize the test so that it accepts either the line with
the function call or the line after, instead of making it
depend on a specific target.