From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFC] Add possibility to stop at thread events
Date: Thu, 03 Sep 2009 02:50:00 -0000 [thread overview]
Message-ID: <m3eiqoivwg.fsf@fleche.redhat.com> (raw)
In-Reply-To: <000301ca2be3$f534a8c0$df9dfa40$@u-strasbg.fr> (Pierre Muller's message of "Wed, 2 Sep 2009 17:42:20 +0200")
>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:
Pierre> The patch below adds the possibility to stop
Pierre> the debuggee each time a thread is created or exited.
Pierre> + add_setshow_zinteger_cmd ("stop-on-thread-events", class_support,
Pierre> + &stop_on_thread_events, _("\
Did you consider making this a "catch" command instead? And
consequently having it show up in "info break"?
I think catch commands are preferable to other ad hoc "stopping"
commands, because users can put commands on a catch, but they can't
readily put commands on something like this.
Tom
prev parent reply other threads:[~2009-09-03 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 15:43 Pierre Muller
2009-09-02 17:22 ` Eli Zaretskii
2009-09-03 2:50 ` Tom Tromey [this message]
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=m3eiqoivwg.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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