From: Fernando Nasser <fnasser@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Fernando Nasser <fnasser@redhat.com>,
Eli Zaretskii <eliz@is.elta.co.il>,
Michael Snyder <msnyder@cygnus.com>,
Daniel Jacobowitz <dmj+@andrew.cmu.edu>,
gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] Testsuite addition for x86 linux GDB and SIGALRM fix
Date: Thu, 26 Jul 2001 10:24:00 -0000 [thread overview]
Message-ID: <3B6051D1.9297BBC0@cygnus.com> (raw)
In-Reply-To: <3B604DD6.9080708@cygnus.com>
Andrew Cagney wrote:
>
> >
> > All are the same. "step" gets into foo(), a "finish" finishes foo(),
> > but then there is bar() so you stop there next. Another "finish" and
> > you will stop on the line that follows the above lines.
> >
> > Note that a "finishi" command would leave you at the return point at
> > some PC in the middle of the above source lines.
>
> So what happens if you're sitting in foo() and type finish but the
> previous command wasn't step. Do you still find yourself in bar()?
>
The current model is that one can switch between the source and assembler debugging at any time by issuing a control command with "i" or without it. So the previous command does not matter -- what matters is if you issued "finish" or "finishi".
> >
> > 'step' should never leave you in the same line from where you've issued
> > it. That is counter intuitive, even if you had a stop-finish in the
> > middle.
>
> This actually throws me. Reading it one way it suggests that ``step ;
> finish'' should have special behavour. See question above.
>
No (see above).
> Anyway try thinking of ``finish'' as a special form of step. What
> happens if you step through foo()? When foo() exits do you jump to
> bar() or go back to the caller?
>
"step" over a subroutine return should behave like "finish" from any other point in that subroutine. A "stepi" should do what "finishi" would do.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-07-26 10:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200005192321.e4JNLEv13368@delius.kettenis.local>
2001-06-27 22:22 ` Andrew Cagney
2001-06-28 10:54 ` Michael Snyder
2001-07-09 14:21 ` Fernando Nasser
2001-07-09 14:34 ` Daniel Jacobowitz
[not found] ` <3B4A2C7C.85C688C4@cygnus.com>
2001-07-09 15:17 ` Daniel Jacobowitz
2001-07-09 15:28 ` Fernando Nasser
2001-07-25 16:11 ` Michael Snyder
2001-07-25 16:45 ` Fernando Nasser
2001-07-25 18:48 ` Andrew Cagney
2001-07-26 7:14 ` Fernando Nasser
2001-07-26 7:44 ` Eli Zaretskii
2001-07-26 7:51 ` Eli Zaretskii
2001-07-26 8:18 ` Eli Zaretskii
2001-07-26 8:48 ` Fernando Nasser
2001-07-26 8:56 ` Eli Zaretskii
2001-07-26 10:21 ` Fernando Nasser
2001-07-26 10:38 ` Fernando Nasser
2001-07-26 10:06 ` Andrew Cagney
2001-07-26 10:24 ` Fernando Nasser [this message]
2001-07-26 10:45 ` Andrew Cagney
2001-07-26 10:54 ` Fernando Nasser
2001-07-26 6:10 ` Michael Snyder
2001-07-26 7:14 ` Fernando Nasser
2001-07-26 7:45 ` Michael Snyder
2001-07-26 7:51 ` Fernando Nasser
[not found] <200106281927.MAA29407@stanley.cygnus.com>
2001-06-28 12:41 ` Stan Shebs
2001-06-28 13:02 Michael Elizabeth Chastain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B6051D1.9297BBC0@cygnus.com \
--to=fnasser@cygnus.com \
--cc=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--cc=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=msnyder@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox