From: Fernando Nasser <fnasser@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Andrew Cagney <ac131313@cygnus.com>,
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 08:48:00 -0000 [thread overview]
Message-ID: <3B603B33.B9B33633@redhat.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010726180932.2195D-100000@is>
Eli Zaretskii wrote:
>
> On Thu, 26 Jul 2001, Fernando Nasser wrote:
>
> > > o step executes instructions until you
> > > leave the current line
> > > (be it enter a function or reach a new
> > > line)
> > >
> >
> > '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.
>
> Agreed.
>
> > "finish" is a source level command and source level commands should not
> > leave you in the middle of source lines.
>
> I'm not sure I understand what you mean here (or that you mean what I
> understand ;-). We could have a source line like this:
>
> int i = (foo (), bar ());
>
> or even like this:
>
> int i = foo (); bar ();
>
> Where would you suggest that "finish" leaves you in these cases, and what
> does ``in the middle of source lines'' mean in these cases? Also, do you
> think these two cases are fundamentally different from "foo (bar ());",
> and if so, how are they different?
>
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.
> > When the user issues a "step" on 'foo (bar ())' source line, he/she may
> > want to enter either bar() or foo(). We cannot know that, so we must
> > stop at each one and he/she can go to the next by issuing "finish",
> > i.e., "finish _this_ subroutine".
>
> Now I'm confused: this seems to suggest that the first "step" gets her
> inside bar(), and if she then types "finish", she will be after the call
> to bar(), but before the call to foo() (that's how I interpret ``finish
> _this_ subroutine''). But that is in the middle of a source line, which
> seems to contradict your previous requirement.
>
No, that would be a "finishi" (assemble level debugging). For the
"finish (source level debugging) see above.
Regards,
Fernando
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-07-26 8:48 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 [this message]
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
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=3B603B33.B9B33633@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@cygnus.com \
--cc=dmj+@andrew.cmu.edu \
--cc=eliz@is.elta.co.il \
--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