From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [patch 2/2] Do not bpstat_clear_actions on throw_exception #3
Date: Fri, 26 Aug 2011 17:38:00 -0000 [thread overview]
Message-ID: <m3d3fst6p1.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201108261245.32822.pedro@codesourcery.com> (Pedro Alves's message of "Fri, 26 Aug 2011 12:45:32 +0100")
Pedro> I think the neatest fix would be to add some try/catch/finaly
Pedro> syntax to the cli. There was a patch for that posted eons ago:
Pedro> http://sourceware.org/ml/gdb-patches/2001-12/msg00449.html
This is also languishing in bugzilla.
I think it would be a decent addition. While I tend to think that more
serious scripting should be done in Python now, I think there is also
room for CLI stuff. (I don't have a hard-and-fast rule here; I don't
want to try to expand the CLI into a full-blown language, but I don't
mind additions much either.)
This won't address Jan's use case, but you dug up another patch that
does, so all is well :)
FWIW I wrote a simple "ignore-errors" command in Python to satisfy my
own occasional need for this.
Jan> (a) throw_exception will call bpstat_clear_actions only if
Jan> exception.error is not NOT_AVAILABLE_ERROR (adding later my new
Jan> ENTRY_VALUE_NOT_AVAILABLE).
Pedro> I don't like this at all.
Me neither. This code has really got to go.
Tom
next prev parent reply other threads:[~2011-08-26 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 14:52 Jan Kratochvil
2011-08-22 17:06 ` Pedro Alves
2011-08-23 20:33 ` Jan Kratochvil
2011-08-24 10:19 ` Pedro Alves
2011-08-26 10:14 ` Jan Kratochvil
2011-08-26 11:45 ` Pedro Alves
2011-08-26 13:17 ` Jan Kratochvil
2011-08-26 13:51 ` Pedro Alves
2011-08-26 17:38 ` Tom Tromey [this message]
2011-08-26 21:04 ` Jan Kratochvil
2011-08-26 21:36 ` Pedro Alves
2011-08-26 21:46 ` Jan Kratochvil
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=m3d3fst6p1.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@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