Re: Watchpoints stopping GDB on specific threads

[Daniel Jacobowitz <drow@false.org>]

On Tue, Aug 14, 2007 at 01:20:58PM -0300, Luis Machado wrote:
> At a first glance, i'd need to work in a different way than the
> breakpoint case, because the entire watchpoint expression is handled by
> a expression parser. It automatically processes the "thread <id>"
> parameter and of course gives an error because that's not recognized. Do
> you have any idea on how this could be solved in a clever way? We could
> start parsing the expression from the end, and try to locate the "thread
> <id>" parameter, and then hand over the remaining parameters to the
> expression parser. What do you think?

You might want to take a look at this:

  http://sourceware.org/ml/gdb-patches/2005-04/msg00092.html

break *EXPRESSION thread N is the same as watch EXPRESSION thread N.
Eli suggested basically the same thing you did; it might work :-)

-- 
Daniel Jacobowitz
CodeSourcery