This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Watchpoints stopping GDB on specific threads
- From: Luis Machado <luisgpm at linux dot vnet dot ibm dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: gdb at sourceware dot org
- Date: Tue, 14 Aug 2007 17:18:49 -0300
- Subject: Re: Watchpoints stopping GDB on specific threads
- References: <1187108458.4388.14.camel@localhost> <usl6ldhv1.fsf@gnu.org>
- Reply-to: luisgpm at linux dot vnet dot ibm dot com
On Tue, 2007-08-14 at 22:41 +0300, Eli Zaretskii wrote:
> > 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?
Using the "if" statement? But in which kind of variable? A user defined
variable on GDB or a variable inside the inferior?
--
Luis Machado
Software Engineer
IBM Linux Technology Center
LoP Toolchain/Debuggers' team
Phone: +55 19-2132-2218
T/L: 839-2218
e-mail: luisgpm@linux.vnet.ibm.com