[RFC]: x86 threaded watchpoint support [2/3]
Tue Jun 15 04:23:00 GMT 2004
> Date: Mon, 14 Jun 2004 17:40:20 -0400
> From: Jeff Johnston <email@example.com>
> The change is needed because with the threading model, you can have multiple
> events to process. So, if you check your watchpoint values, all of them may
> have changed but you end up reporting an invalid thread location. For example,
> I was getting watchpoints changing at the same time of a new thread event (it
> couldn't discern). The reported location was __nptl_create_event (not very
Does this mean that when a watchpoint breaks, it stops only the thread
that hit the watchpoint, while other threads continue to run?
If all threads stop, then there could not be multiple events, unless
we are talking about a machine with more than one CPU.
Or am I missing something?
> I have talked to Andrew and he suggests that the target_stopped_data_address
> code should be modified to add a status code instead of the current 0 addr
> return value.
That plan is okay with me, but I suggest to run the design by us
before you start coding, in case there are platforms out there that
need some adjustments in what you intend to do.
More information about the Gdb-patches