From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sourceware.org
Cc: Daniel Jacobowitz <drow@false.org>,
Markus Schiltknecht <markus@bluegap.ch>,
Bob Rossi <bob@brasko.net>
Subject: Re: minimalistic MI catch support
Date: Thu, 09 Feb 2006 06:28:00 -0000 [thread overview]
Message-ID: <17386.57501.980555.996896@kahikatea.snap.net.nz> (raw)
[I srewed up the header first time, hopefully not this time, apologies if you
get two copies. I'm not subscribed to gdb-patches and would like to be cc'ed
in any threads on MI, if possible.]
I've not used catchpoints, so I just have a couple of minor observations.
> case bp_catch_vfork:
> annotate_catchpoint (bs->breakpoint_at->number);
> - printf_filtered (_("\nCatchpoint %d (vforked process %d), "),
> - bs->breakpoint_at->number,
> - bs->breakpoint_at->forked_inferior_pid);
> + ui_out_text (uiout, "\nCatchpoint ");
> + if (ui_out_is_mi_like_p (uiout))
> + ui_out_field_string (uiout, "reason",
> + async_reason_lookup (EXEC_ASYNC_BREAKPOINT_HIT));
> + ui_out_field_int (uiout, "bkptno", bs->breakpoint_at->number);
> + ui_out_text (uiout, " (vforked process ");
> + ui_out_field_int (uiout, "vforked-process",
> + bs->breakpoint_at->forked_inferior_pid);
I realise that this method of combining CLI and MI output is already used in
breakpoint.c but presumably it has the unfortunate side effect of not
translating some CLI output intended for the user. For example "breakpoint"
and "catchpoint may be translated in some places but not others.
The manual says:
`exec'
A call to `exec'. This is currently only available for HP-UX.
`fork'
A call to `fork'. This is currently only available for HP-UX.
`vfork'
A call to `vfork'. This is currently only available for
HP-UX.
Is that still true? I can certainly set catchpoints for these with GNU/Linux.
> > *stopped,reason="catchpoint-hit",catchpoint-kind="vfork",bkptno="1",forked-process="6570",thread-id="0",frame={addr="0x00002aaaaaeb6462",func="fork",args=[],from="/lib/libc.so.6"}
> I like this.
With reason="breakpoint-hit" it's nature (catch vfork) can be deduced from
bkptno="1" and -break-list or just "-break-info 1" but I guess there's no harm
in redundant information.
Nick http://www.inet.net.nz/~nickrob
next reply other threads:[~2006-02-09 6:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 6:28 Nick Roberts [this message]
2006-02-10 6:34 ` Nick Roberts
2006-02-10 11:25 ` Eli Zaretskii
2006-02-10 14:11 ` Daniel Jacobowitz
2006-02-10 15:41 ` Eli Zaretskii
2006-02-10 16:48 ` Daniel Jacobowitz
2006-02-10 18:40 ` Eli Zaretskii
2006-02-10 18:52 ` Daniel Jacobowitz
2006-02-10 20:17 ` Nick Roberts
2006-02-10 20:20 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2006-01-28 13:04 Markus Schiltknecht
2006-02-06 23:29 ` Daniel Jacobowitz
2006-02-07 1:15 ` Bob Rossi
2006-02-07 3:00 ` Daniel Jacobowitz
2006-02-07 12:01 ` Markus Schiltknecht
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=17386.57501.980555.996896@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=markus@bluegap.ch \
/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