Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] Testsuite addition for x86 linux GDB and SIGALRM fix
Date: Mon, 09 Jul 2001 15:28:00 -0000	[thread overview]
Message-ID: <3B4A300A.BD2269AE@cygnus.com> (raw)
In-Reply-To: <20010709151725.A19811@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> On Mon, Jul 09, 2001 at 06:13:16PM -0400, Fernando Nasser wrote:
> > > Stepping in to bar, typing finish,
> > > and ending up after the call to foo would be exceedingly non-intuitive.
> > >
> >
> > This is true. But a finish would not stop after the call to foo() in
> > this case.  The stepping would be aborted as we entered foo() itself
> > (note that I said "step", not "next").  The result is quite intuitive
> > in this case and you just provided one good example of how we could
> > use it -- one could go "finish"-ing until the desired function was
> > entered (without the need to step again and without the weird thing
> > of appearing to stop at the same line you were before).
> 
> I personally think that this would be more confusing - I finish a
> function and end up, not in its caller, but in some other function
> called from the caller?  But I've no strong opinion; both options seem
> a little clunky.
> 

Of course, this could be made an option, so different tastes are accommodated (default to current behavior).  But I won't have time to implement it in the near future, so you don't have to worry about it :-)

Regards and thanks for the comments,
Fernando

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2001-07-09 15:28 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 [this message]
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
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=3B4A300A.BD2269AE@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=dmj+@andrew.cmu.edu \
    --cc=gdb-patches@sourceware.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