Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [5/9] Associate parsed condition with location
Date: Sat, 08 Sep 2007 11:12:00 -0000	[thread overview]
Message-ID: <u4pi5s977.fsf@gnu.org> (raw)
In-Reply-To: <200709080042.24484.vladimir@codesourcery.com> (message from 	Vladimir Prus on Sat, 8 Sep 2007 00:42:24 +0400)

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 8 Sep 2007 00:42:24 +0400
> 
> 	* breakpoint.c: Adjust.
> 	* tui/tui-winsource.c: Adjust.

Nitpicking: these aren't, strictly speaking, valid ChangeLog entries,
because they don't name the functions where the changes were made.

> --- gdb/breakpoint.h	(/work/mb_mainline/4_bpstat_owner)	(revision 4741)
> +++ gdb/breakpoint.h	(/work/mb_mainline/5_per_loc_cond)	(revision 4741)
> @@ -243,6 +243,13 @@ struct bp_location
>       than reference counting.  */
>    struct breakpoint *owner;
>  
> +  /* Conditional.  Break only if this expression's value is nonzero.  
> +     Unlike string form of condition, which is associated with breakpoint,
> +     this is associated with location, since if breakpoint has several
> +     PC locations, the evaluation of expression can be different for
> +     different PCs.  */
> +  struct expression *cond;

I think we should use ``location'' instead of ``PC'', since you make
the change for watchpoints as well, where the PC is irrelevant.


  reply	other threads:[~2007-09-08 11:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 20:42 Vladimir Prus
2007-09-08 11:12 ` Eli Zaretskii [this message]
2007-09-08 11:27   ` Vladimir Prus
2007-09-08 12:17     ` Eli Zaretskii
2007-09-08 13:46       ` Daniel Jacobowitz
2007-09-08 16:17         ` Eli Zaretskii
2007-09-08 16:50           ` Daniel Jacobowitz
2007-09-22 17:53   ` Vladimir Prus
2007-09-22 18:33     ` Eli Zaretskii
2007-09-22 18:43       ` 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=u4pi5s977.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.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