public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: Jim Blandy <jimb@red-bean.com>, Project Archer <archer@sourceware.org>
Subject: Re: feature idea: upto
Date: Thu, 23 Jul 2009 18:52:00 -0000	[thread overview]
Message-ID: <m363djbaxl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20090723181434.12C1580560@magilla.sf.frob.com> (Roland McGrath's message of "Thu\, 23 Jul 2009 11\:14\:34 -0700 \(PDT\)")

>>>>> "Roland" == Roland McGrath <roland@redhat.com> writes:

Roland> But non-nesting "end" parsing means I can't write:
[...]

This should work.  It is a bug that it doesn't.

Roland> In particular "catch throw" is comically no more useful than "b
Roland> __cxa_throw" and it would seem most natural for it to do
Roland> something like the "up" automagically.

We discussed this a little.  My recollection is that Daniel tried this
but concluded that MI clients get confused when gdb stops and the
selected frame is not the newest frame.  So, some kind of MI extension
or change is needed.

I don't think we pursued it past that, though it is still nominally on
our to-do list.  Also it is:
http://sourceware.org/bugzilla/show_bug.cgi?id=9599

Tom

  reply	other threads:[~2009-07-23 18:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 22:34 Roland McGrath
2009-07-07 16:18 ` [python] implement "upto" (Was: feature idea: upto) Tom Tromey
2009-07-09  4:25   ` Roland McGrath
2009-07-17 22:06     ` [python] implement "upto" Tom Tromey
2009-07-20  6:17       ` Roland McGrath
2009-07-23  7:00 ` feature idea: upto Jim Blandy
2009-07-23 18:15   ` Roland McGrath
2009-07-23 18:52     ` Tom Tromey [this message]
2009-07-23 19:08       ` Roland McGrath

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=m363djbaxl.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=archer@sourceware.org \
    --cc=jimb@red-bean.com \
    --cc=roland@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).