From: Daniel Jacobowitz <dan@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: Jim Blandy <jimb@codesourcery.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Don't reset watchpoint block on solib load.
Date: Tue, 29 Jan 2008 15:23:00 -0000 [thread overview]
Message-ID: <20080129151715.GA28121@caradoc.them.org> (raw)
In-Reply-To: <200801231257.27977.vladimir@codesourcery.com>
On Wed, Jan 23, 2008 at 12:57:27PM +0300, Vladimir Prus wrote:
> So, I guess the solutions are either:
>
> 1. Omit the move of condition parsing from this patch, or
> 2. Keep condition parsing in this patch, and then commit
> the use-multiple-locations-for-watchpoint patch which will
> immediately make condition only reparsed when breakpoint_re_set_one
> is called.
>
> Given that use-multiple-locations-for-watchpoint patch is
> approved except for the bit that makes reparsing of condition
> optional, it seems that (2) is less work.
All this sounds fine to me. I'm OK with this patch, which I believe
is the one here:
http://sourceware.org/ml/gdb-patches/2007-11/msg00522.html
> For convenience, I attach the current version of
> use-multiple-locations-for-watchpoint patch. The difference
> to the previous revision is as follows:
>
>
> @@ -966,7 +966,7 @@ update_watchpoint (struct breakpoint *b, int reparse)
> value_free (v);
> }
>
> - if (b->cond_string != NULL)
> + if (reparse && b->cond_string != NULL)
> {
> char *s = b->cond_string;
> if (b->loc->cond)
>
>
> Dan, is the patch still OK to commit?
Yes, it is.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-29 15:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 17:14 Vladimir Prus
2007-11-27 23:00 ` Jim Blandy
2007-11-28 15:59 ` Vladimir Prus
2007-11-28 16:23 ` Vladimir Prus
2007-11-28 19:46 ` Jim Blandy
2007-11-28 20:04 ` Vladimir Prus
2007-11-28 22:37 ` Jim Blandy
2007-11-29 6:09 ` Vladimir Prus
2007-11-28 22:50 ` Jim Blandy
2007-11-28 22:18 ` Jim Blandy
2007-11-29 4:24 ` Eli Zaretskii
2007-11-29 7:04 ` Vladimir Prus
2007-11-29 18:54 ` Jim Blandy
2007-11-29 19:03 ` Variable identification (Was: [RFA] Don't reset watchpoint block on solib load.) Vladimir Prus
2007-11-30 1:22 ` Michael Snyder
2007-11-30 5:52 ` Vladimir Prus
2007-11-30 20:53 ` Eli Zaretskii
2007-12-01 1:39 ` Variable identification Jim Blandy
2007-12-01 1:47 ` Michael Snyder
2008-01-16 1:29 ` [RFA] Don't reset watchpoint block on solib load Jim Blandy
2008-01-23 9:58 ` Vladimir Prus
2008-01-29 15:23 ` Daniel Jacobowitz [this message]
2007-11-29 6:55 ` Vladimir Prus
2007-11-29 18:40 ` Jim Blandy
2007-11-29 18:45 ` Vladimir Prus
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=20080129151715.GA28121@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@codesourcery.com \
--cc=vladimir@codesourcery.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