From: Joel Brobecker <brobecker@adacore.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [Patch] Watchpoint condition fix
Date: Thu, 17 Apr 2008 21:09:00 -0000 [thread overview]
Message-ID: <20080417205708.GA12735@adacore.com> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04E1BCE9@ecamlmw720.eamcs.ericsson.se>
> > As a result, the temporary variable "s" shouldn't be necessary
> > either.
>
> I'm not sure about this one. s is pointing to b->cond_string
> and not b->loc->cond. Is it really unecessary?
You are right to keep it, but not for the reason you explained.
I forgot that parse_exp_1 advances the string pointer that it is given.
So if we didn't keep the temporary variable, we would screw b->cond_string
(oops!).
> 2008-04-17 Marc Khouzam <marc.khouzam@ericsson.com>
>
> * breakpoint.c (update_watchpoint): Always reparse
> condition.
This is OK after having fixed a tiny little detail:
> - if (reparse && b->cond_string != NULL)
> + /* We just regenerated the list of breakpoint locations.
> + * The new location does not have its condition field set to anything
> + * and therefore, we must always reparse the cond_string, independently
> + * of the value of the reparse flag.
Reformat the comment to avoid the '*' at the beginning of each line
and put the final '*/' at the end of the last line, not on a new line:
/* We just regenerated the list of breakpoint locations.
The new location does not have its condition field set to anything
and therefore, we must always reparse the cond_string, independently
of the value of the reparse flag. */
Thank you,
--
Joel
next prev parent reply other threads:[~2008-04-17 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 14:21 Marc Khouzam
2008-04-16 22:15 ` Joel Brobecker
2008-04-17 18:48 ` Marc Khouzam
2008-04-17 21:09 ` Joel Brobecker [this message]
2008-04-18 10:10 ` Marc Khouzam
2008-04-19 1:39 ` Doug Evans
2008-04-19 1:58 ` Joel Brobecker
2008-04-22 20:36 ` Joel Brobecker
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=20080417205708.GA12735@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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