[RFA]: Modified Watchthreads Patch
Sat Dec 11 21:54:00 GMT 2004
Date: Sat, 11 Dec 2004 13:02:36 -0500
From: Daniel Jacobowitz <firstname.lastname@example.org>
On Sat, Dec 11, 2004 at 07:52:08PM +0200, Eli Zaretskii wrote:
> > Date: Sat, 11 Dec 2004 11:52:37 -0500
> > From: Daniel Jacobowitz <email@example.com>
> > Cc: Jeff Johnston <firstname.lastname@example.org>, email@example.com
> > - The GDB core needs to continue to support watchpoints (hardware
> > breakpoints; et cetera) triggering in an unexpected thread.
> > Rationale: some targets won't support any other way. For instance
> > page protection based watchpoints on GNU/Linux would probably apply to
> > all threads.
> Another, even better (IMHO) rationale: one important reason for using
> watchpoints is to find what code accesses some specific data; when we
> use watchpoints for this, we more often than not do not know what
> thread will access the data.
That's just a watchpoint without an explicit thread specified. That's
the default when you say "watch foo".
> Yes, but I think (and have said it several times in the past) that
> this difference in handling bp_hardware_watchpoint and
> bp_read_watchpoint/bp_access_watchpoint is a Bad Thing and we should
> rewrite it so that all the types of hardware-assisted watchpoints are
> handled in the same way. The current code that handles
> bp_hardware_watchpoint is simply the same code that handled software
> bp_watchpoint, which to me doesn't make sense, because at least on
> x86, the hardware tells us exactly what address was written to.
> (However, note that some platforms that cannot implement
> target_stopped_data_address actually take advantage of the different
> treatment of bp_hardware_watchpoint to implement `watch' even though
> `rwatch' and `awatch' are not implemented. If we decide to make the
> treatment of all hardware-assisted watchpoints similar, we should be
> careful not to break those platforms.)
Yes, page-protection assisted watchpoints in their most primitive form
might cause spurious events when you access memory that is in the same
page as the variable being watched. GDB will have to check whether
the variable actually changed.
OK. We can fix this.
But for the reason given above `watch' always will be a bit different
than `rwatch' and `awatch'.
> > Assuming that the program didn't stop for any other reason, and that
> > hardware watchpoints trigger after the write is executed
> (I note in parens that on x86, watchpoints trigger _before_ the write
> is executed. Not sure if it matters here.)
This is in general true for page-protection assisted watchpoints to.
At least it is for HP-UX. You get a page fault which is reported as
SIGBUS or SIGSEGV or something like that. But I guess that for real
hardware watchpoints it is possible for them to trigger after the
write is executed. And for page-protection assisted watchpoints that
are implemented fully in the kernel this is possible behaviour. I
think this is what happens on Solaris, but I'm not completely sure.
How do we get the "new value" for a watchpoint, then? Do we step over
In general yes. This is what HAVE_STEPPABLE_WATCHPOINT,
HAVE_NONSTEPPABLE_WATCHPOINT and HAVE_CONTINUABLE_WATCHPOINT are
> > or come up with a more useful behavior for software and hardware
> > watchpoints than the one I've thought of. Can you think of one?
> I think there's nothing wrong with the model you suggested, it's just
> that our handling of bp_hardware_watchpoint is wrong. Assuming we
> change it along the lines I suggested above, do you see any further
> problems with extending watchpoints to threaded programs?
This is "extending watchpoints to specific threads" in my
understanding, not to "threaded programs" - obviously a useful feature,
but I think a different one. Conceptually, our watchpoints already
work for threaded programs. In practice, Jeff found that on GNU/Linux
they didn't work, and that's what he's fixing, not the "specific
threads" enhancement. Does that make sense?
It does to me. If there are problems they're most likely in
platform-dependent code (and i386-nat.c *is* platform-dependent code
even if it's used on a number of different platforms).
> One aspect where a kernel can help us with multi-threaded programs is
> if it tells us not only that a watchpoint has been hit, but also what
> thread hit that watchpoint. Are there any kernel-level features that
> can be used to find that out?
Right now GDB assumes that this is reflected in inferior_ptid. At
least for GNU/Linux, this is a reasonable assumption. The watchpoint
is reported as an event (SIGTRAP); an event has to come from a specific
thread, and it will come from the thread which generated the
I think this is a valid assumption. Hitting a "hardware" watchpoint
will always trigger some sort of trap (be it a memory fault or some
special hardware interrupt). A Unix-like kernel should know what
"thread" was active at that point, and be able to report that.
More information about the Gdb-patches