Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: gdb@sources.redhat.com
Subject: Re: Remote set thread breakpoint
Date: Wed, 08 Sep 2004 14:21:00 -0000	[thread overview]
Message-ID: <413F155B.6070003@gnu.org> (raw)
In-Reply-To: <5.2.0.9.1.20040908160444.01d4c920@NT_SERVER>

> Hi
> 
> I'm thinking about extending the remote protocol for thread breakpoints.
> The easiest solution would be to just add another data field to the Z
> commands, like:
> 
> Ztype,addr,length,threadid
> 
> If threadid is given, gdbserver can use it. If it's -1 or not present (as in
> the present implementation) it's a global breakpoint.
> 
> But if this would cause incompatibilities with existing parsers it may
> be better to create a new command, even if it's just Z5 and the rest
> is the same.
> 
> What would be better? Or is something like that already in the pipe?

Yes [zZ]5 would be safer.  Would also be a good oportunity to formalize 
how to probe support for this packet - Z5?  Given things like vCont and 
its vCont? query, a [better?] alternative might be be vBP...

Just note that there is a small challenge here.  GDB internally assumes 
that breakpoints are global (it's a limitation / bug) - you'll need to 
also investigate  what needs to be changed closer to GDB's core.

Andrew



  reply	other threads:[~2004-09-08 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-08 14:12 Fabian Cenedese
2004-09-08 14:21 ` Andrew Cagney [this message]
2004-09-08 15:14   ` Fabian Cenedese
2004-09-13 13:03   ` Fabian Cenedese

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=413F155B.6070003@gnu.org \
    --to=cagney@gnu.org \
    --cc=Cenedese@indel.ch \
    --cc=gdb@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