From: Pedro Alves <pedro@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Somewhat sanitize watchpoints with conditions on local expressions
Date: Thu, 04 Mar 2010 16:05:00 -0000 [thread overview]
Message-ID: <201003041604.53513.pedro@codesourcery.com> (raw)
In-Reply-To: <E1Nn5u2-0006TS-0i@fencepost.gnu.org>
On Thursday 04 March 2010 07:55:26, Eli Zaretskii wrote:
> > +static int
> > +is_watchpoint (struct breakpoint *bpt)
> > +{
> > + return (is_hardware_watchpoint (bpt)
> > + || bpt->type == bp_watchpoint);
> > +}
>
> Does this catch read and access watchpoints? Should it?
It does, and it should. I've added the below to the patch.
--
Pedro Alves
Index: src/gdb/breakpoint.c
===================================================================
--- src.orig/gdb/breakpoint.c 2010-03-04 16:03:30.000000000 +0000
+++ src/gdb/breakpoint.c 2010-03-04 16:03:09.000000000 +0000
@@ -921,6 +921,8 @@ insert_catchpoint (struct ui_out *uo, vo
b->ops->insert (b);
}
+/* Return true if BPT is of any hardware watchpoint kind. */
+
static int
is_hardware_watchpoint (struct breakpoint *bpt)
{
@@ -929,6 +931,9 @@ is_hardware_watchpoint (struct breakpoin
|| bpt->type == bp_access_watchpoint);
}
+/* Return true if BPT is of any watchpoint kind, hardware or
+ software. */
+
static int
is_watchpoint (struct breakpoint *bpt)
{
prev parent reply other threads:[~2010-03-04 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 3:50 Pedro Alves
2010-03-04 5:59 ` Joel Brobecker
2010-03-04 7:57 ` Eli Zaretskii
2010-03-04 16:00 ` Pedro Alves
2010-03-04 16:12 ` Pedro Alves
2010-03-04 16:19 ` Pedro Alves
2010-03-04 16:23 ` Pedro Alves
2010-03-08 6:34 ` Joel Brobecker
2010-03-10 13:27 ` Pedro Alves
2010-03-04 7:55 ` Eli Zaretskii
2010-03-04 16:05 ` Pedro Alves [this message]
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=201003041604.53513.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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