Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] bpstat_do_actions in one place
Date: Wed, 07 May 2008 19:50:00 -0000	[thread overview]
Message-ID: <20080507113736.GA32080@caradoc.them.org> (raw)
In-Reply-To: <u3aoufso1.fsf@gnu.org>

On Wed, May 07, 2008 at 11:02:38AM +0300, Eli Zaretskii wrote:
> That this instance of `backtrace' be aborted, and the loop will
> continue.

Interesting.  That's not what I would expect; for instance, I'd
expect an entire user-defined ("define") command to be aborted.

If that happened, how would you stop the example I gave?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-07 11:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 19:08 Vladimir Prus
2008-05-02  2:58 ` Daniel Jacobowitz
2008-05-05  9:56   ` Vladimir Prus
2008-05-05 13:06     ` Daniel Jacobowitz
2008-05-05 13:10       ` Vladimir Prus
2008-05-05 14:12         ` Daniel Jacobowitz
2008-05-05 20:47         ` Eli Zaretskii
2008-05-05 20:47           ` Daniel Jacobowitz
2008-05-05 20:53             ` Eli Zaretskii
2008-05-05 20:57               ` Daniel Jacobowitz
2008-05-06 15:46                 ` Eli Zaretskii
2008-05-06 15:47                   ` Daniel Jacobowitz
2008-05-06 19:24                     ` Eli Zaretskii
2008-05-06 20:04                       ` Daniel Jacobowitz
2008-05-07 11:38                         ` Eli Zaretskii
2008-05-07 19:50                           ` Daniel Jacobowitz [this message]
2008-05-08  4:23                             ` Eli Zaretskii
2008-05-08  5:46                               ` Daniel Jacobowitz
2008-05-08 11:34                                 ` Eli Zaretskii

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=20080507113736.GA32080@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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