From: Eli Zaretskii <eliz@gnu.org>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb@sourceware.org
Subject: Re: Watchpoints stopping GDB on specific threads
Date: Tue, 14 Aug 2007 19:41:00 -0000 [thread overview]
Message-ID: <usl6ldhv1.fsf@gnu.org> (raw)
In-Reply-To: <1187108458.4388.14.camel@localhost> (message from Luis Machado on Tue, 14 Aug 2007 13:20:58 -0300)
> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Date: Tue, 14 Aug 2007 13:20:58 -0300
>
> I'm looking forward to have the same functionality for watchpoints. So
> whenever GDB detects a watchpoint trigger, it would verify the current
> thread and would stop only if the thread matches the ID we provided in a
> command like "watch <address> thread <id>". if no ID is provided, GDB
> would stop at every thread as usual (assuming a threaded watchpoint
> support).
Unless I misunderstand something fundamental, if the current thread ID
is in some variable, you could define a condition for a watchpoint,
no?
next prev parent reply other threads:[~2007-08-14 19:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 16:21 Luis Machado
2007-08-14 16:42 ` Daniel Jacobowitz
2007-08-14 19:41 ` Eli Zaretskii [this message]
2007-08-14 19:47 ` Daniel Jacobowitz
2007-08-14 20:19 ` Luis Machado
2007-08-15 3:06 ` Eli Zaretskii
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=usl6ldhv1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.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