From: "Siva Velusamy" <siva.velusamy@gmail.com>
To: gdb@sourceware.org
Subject: rwatchpoint configuration
Date: Tue, 18 Dec 2007 00:43:00 -0000 [thread overview]
Message-ID: <e7dfeff00712171642k477c0069r51e886d80952f34f@mail.gmail.com> (raw)
Hello,
I am debugging a read watchpoint issue on an embedded target (Xilinx
MicroBlaze processor).
The issue I'm trying to resolve is that gdb breaks on a read
watchpoint _only_ if the value of the variable being watched has not
changed since the watchpoint was set. This comes from the following
condition in gdb:
gdb/breakpoint.c:2792
case WP_VALUE_CHANGED:
if (b->type == bp_read_watchpoint)
{
/* Don't stop: read watchpoints shouldn't fire if
the value has changed. This is for targets
which cannot set read-only watchpoints. */
bs->print_it = print_it_noop;
bs->stop = 0;
continue;
}
Since the MicroBlaze target can indeed set read-only watchpoints, this
should not happen. It looks as if the target has not been properly
configured. Could someone point me to the appropriate configuration
settings and what the correct values should be for a processor that
natively supports read watchpoints?
Note that read watchpoints do work fine if the value has not changed
since the breakpoint was set. Also, the serial protocol packet
received looks like "T05watch:000014ec;" in one specific test when the
read watchpoint is hit.
Thanks,
Siva
--
In the end, everything is a gag.
Charlie Chaplin
next reply other threads:[~2007-12-18 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 0:43 Siva Velusamy [this message]
2007-12-18 0:48 ` Daniel Jacobowitz
2007-12-18 0:53 ` Siva Velusamy
2007-12-18 0:59 ` Siva Velusamy
2007-12-18 2:27 ` Daniel Jacobowitz
2007-12-18 4:16 ` Eli Zaretskii
2007-12-18 4:23 ` Eli Zaretskii
2007-12-18 7:22 ` Siva Velusamy
2007-12-18 4:19 ` Eli Zaretskii
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=e7dfeff00712171642k477c0069r51e886d80952f34f@mail.gmail.com \
--to=siva.velusamy@gmail.com \
--cc=gdb@sourceware.org \
/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