From: Vladimir Prus <vladimir@codesourcery.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: Aleksandar Ristovski <aristovski@qnx.com>,
gdb-patches@sources.redhat.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch/MI] Implementation for break-catch command
Date: Sun, 01 Jun 2008 05:15:00 -0000 [thread overview]
Message-ID: <200806010914.22980.vladimir@codesourcery.com> (raw)
In-Reply-To: <18497.57814.496794.333674@kahikatea.snap.net.nz>
On Sunday 01 June 2008 03:40:06 Nick Roberts wrote:
> > > static void enable_delete_breakpoint (struct breakpoint *);
> > > @@ -6549,13 +6547,16 @@ print_mention_exception_catchpoint (stru
> > > int bp_temp;
> > > int bp_throw;
> > >
> > > - bp_temp = b->loc->owner->disposition == disp_del;
> > > - bp_throw = strstr (b->addr_string, "throw") != NULL;
> > > - ui_out_text (uiout, bp_temp ? _("Temporary catchpoint ")
> > > - : _("Catchpoint "));
> > > - ui_out_field_int (uiout, "bkptno", b->number);
> > > - ui_out_text (uiout, bp_throw ? _(" (throw)")
> > > - : _(" (catch)"));
> > > + if (!ui_out_is_mi_like_p (uiout))
> > > + {
> > > + bp_temp = b->loc->owner->disposition == disp_del;
> > > + bp_throw = strstr (b->addr_string, "throw") != NULL;
> > > + ui_out_text (uiout, bp_temp ? _("Temporary catchpoint ")
> > > + : _("Catchpoint "));
> > > + ui_out_field_int (uiout, "bkptno", b->number);
> > > + ui_out_text (uiout, bp_throw ? _(" (throw)")
> > > + : _(" (catch)"));
> > > + }
> >
> > Uh, seems like there's some messiness in MI here. For ordinary breakpoints,
> > MI installs the 'breakpoint_notify' hook that prints all the information,
> > and 'mention' specifically avoids printing anything for MI. For watchpoints,
> > however, no hooks are installed, and 'mention' does print something --
> > basically just id and expression.
> >
> > For -break-catch, you choose to install hooks, and disable printing anything
> > in 'mention' -- seems fine to me.
>
> I think all these "breakpoints" should be changed to use observers. This
> seems to just add to the ugliness.
They definitely should.
- Volodya
next prev parent reply other threads:[~2008-06-01 5:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 20:59 Aleksandar Ristovski
2008-05-28 21:26 ` Vladimir Prus
2008-05-28 21:36 ` Aleksandar Ristovski
2008-05-28 23:10 ` Eli Zaretskii
2008-05-29 20:46 ` Aleksandar Ristovski
2008-05-29 20:52 ` Aleksandar Ristovski
[not found] ` <200805312006.11811.vladimir@codesourcery.com>
[not found] ` <18497.57814.496794.333674@kahikatea.snap.net.nz>
2008-06-01 5:15 ` Vladimir Prus [this message]
2008-06-02 13:23 ` Aleksandar Ristovski
2008-06-02 14:40 ` Vladimir Prus
2008-06-02 16:06 ` Aleksandar Ristovski
2008-06-02 16:28 ` Vladimir Prus
2008-07-31 14:06 ` Aleksandar Ristovski
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=200806010914.22980.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=aristovski@qnx.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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