From: Paul Koning <pkoning@equallogic.com>
To: gdb@sources.redhat.com
Subject: watchpoint fixes
Date: Thu, 22 May 2003 20:04:00 -0000 [thread overview]
Message-ID: <16077.11595.367005.470124@pkoning.dev.equallogic.com> (raw)
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
reply other threads:[~2003-05-22 20:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=16077.11595.367005.470124@pkoning.dev.equallogic.com \
--to=pkoning@equallogic.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).