From: Andreas Schwab <schwab@suse.de>
To: Frederic RISS <frederic.riss@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New threadnum command for breakpoints
Date: Fri, 28 Jul 2006 14:20:00 -0000 [thread overview]
Message-ID: <jeodv9erq0.fsf@sykes.suse.de> (raw)
In-Reply-To: <20060728141339.GA15103@nevyn.them.org> (Daniel Jacobowitz's message of "Fri, 28 Jul 2006 10:13:40 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Fri, Jul 28, 2006 at 04:03:37PM +0200, Andreas Schwab wrote:
>> Frederic RISS <frederic.riss@st.com> writes:
>>
>> > The attached patch doesn't try to solve the parsing issue, but it simply
>> > adds a 'threadnum' command that one can use to (un)set the thread of a
>> > particular breakpoint. I'm not sure about the command name, because it
>> > will conflict with the thread command. Suggestions appreciated.
>>
>> Make it a subcommand of the thread command.
>
> Hmm, I don't like that much - it's a breakpoint functionality, not a
> thread functionality.
I agree. "set breakpoint" may be a better place.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2006-07-28 14:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 13:44 Frederic RISS
2006-07-28 14:03 ` Andreas Schwab
2006-07-28 14:13 ` Daniel Jacobowitz
2006-07-28 14:20 ` Andreas Schwab [this message]
2006-07-28 14:59 ` Frederic RISS
2006-07-28 15:14 ` Daniel Jacobowitz
2006-07-31 8:32 ` Frederic RISS
2006-07-31 12:53 ` Daniel Jacobowitz
2006-07-31 14:00 ` Frederic RISS
2006-07-31 20:07 ` Frédéric Riss
2006-07-31 20:14 ` Eli Zaretskii
2006-08-08 18:22 ` Daniel Jacobowitz
2006-08-08 19:43 ` Frédéric Riss
2006-08-16 14:15 ` Frederic RISS
2006-08-31 7:23 ` Frederic RISS
2006-07-28 14:28 ` Frederic RISS
2006-07-28 14:30 ` Frederic RISS
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=jeodv9erq0.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=frederic.riss@st.com \
--cc=gdb-patches@sources.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