From: "Eli Zaretskii" <eliz@gnu.org>
To: "Maciej W. Rozycki" <macro@mips.com>, gdb-patches@sources.redhat.com
Subject: Re: Support for "break *ADDRESS thread THREADNO"
Date: Tue, 12 Apr 2005 19:05:00 -0000 [thread overview]
Message-ID: <01c53f92$Blat.v2.4$280330c0@zahav.net.il> (raw)
In-Reply-To: <20050412185549.GA9715@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 12 Apr 2005 14:55:49 -0400)
> Date: Tue, 12 Apr 2005 14:55:49 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: "Maciej W. Rozycki" <macro@mips.com>, gdb-patches@sources.redhat.com
>
> There's already common code for this, that's where most of the 'thread
> THREADNO' support is. I think it's in linespec.c somewhere, but it
> might be in breakpoint.c.
Doing this in one of these two place would be okay, since they are
language independent.
> TBH, the mechanism is fragile; I can't think of a more robust way but
> there must be one.
How about a convenience variable $thread that will hold the current
thread ID? Then we could simply use a condition "if $thread == TID".
Or maybe a command option "break --thread=ID *ADDR". (Or did we
decide to not use such syntax?)
next prev parent reply other threads:[~2005-04-12 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 15:54 Maciej W. Rozycki
2005-04-12 18:13 ` Daniel Jacobowitz
2005-04-12 18:24 ` Maciej W. Rozycki
2005-04-12 18:51 ` Eli Zaretskii
2005-04-12 18:55 ` Daniel Jacobowitz
2005-04-12 19:05 ` Eli Zaretskii [this message]
2005-04-12 19:17 ` Stan Shebs
2005-04-12 19:21 ` Daniel Jacobowitz
2005-04-12 19:22 ` Daniel Jacobowitz
2005-04-13 10:36 ` Maciej W. Rozycki
2005-04-13 12:09 ` Daniel Jacobowitz
2005-04-13 16:05 ` Maciej W. Rozycki
2005-04-13 17:37 ` Eli Zaretskii
2005-04-13 17:41 ` Daniel Jacobowitz
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='01c53f92$Blat.v2.4$280330c0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=macro@mips.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