Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Frederic RISS <frederic.riss@st.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New threadnum command for breakpoints
Date: Fri, 28 Jul 2006 14:28:00 -0000	[thread overview]
Message-ID: <1154096859.28300.255.camel@crx549.cro.st.com> (raw)
In-Reply-To: <jeu051eshy.fsf@sykes.suse.de>

On Fri, 2006-07-28 at 16:03 +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.

I thought of that, but I didn't like it: it mixes breakpoint and thread
functionality in a way that doesn't seem right... but that's just a
personal feeling that we take care not to . You suggest something like:

(gdb) thread breakpoint <bp> <tid>

Anyone else prefers it this way? 

Fred.


  parent reply	other threads:[~2006-07-28 14:28 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
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 [this message]
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=1154096859.28300.255.camel@crx549.cro.st.com \
    --to=frederic.riss@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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