* watchpoint fixes
@ 2003-05-22 20:04 Paul Koning
0 siblings, 0 replies; only message in thread
From: Paul Koning @ 2003-05-22 20:04 UTC (permalink / raw)
To: gdb
Gentlepeople,
A few weeks ago I reported problems in the way hardware watchpoints
work in gdb -- or rather, don't until patched. I described a fix but
have heard no reaction. Should I submit that as a patch to the
patches list? Note that I'm just a gdb observer...
I've noticed some more problems along similar lines: if you set a
watchpoint, and then the program hits a break instruction that doesn't
match a breakpoint set by gdb, the program doesn't stop. The reason
is that it falsely matches the watchpoint but since the data address
doesn't match, the stop_status ends up "keep going". The solution is
simple: if the stop was not a watchpoint (there isn't a data address
from the target) then pretend watchpoints don't exist at all, rather
than marking them as "keep going".
I could submit a patch for that too if there's interest. Suggestions?
paul
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-05-22 20:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-05-22 20:04 watchpoint fixes Paul Koning
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).