Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <vladimir@codesourcery.com>,
		gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix breakpoint condition that use member variables.
Date: Sat, 22 Mar 2008 14:49:00 -0000	[thread overview]
Message-ID: <20080322144931.GA19219@caradoc.them.org> (raw)
In-Reply-To: <u63vehq9d.fsf@gnu.org>

On Sat, Mar 22, 2008 at 02:55:42PM +0200, Eli Zaretskii wrote:
> That could surprise the user.  Is it possible to make an additional
> change to look for possible other interpretations of i_ which are
> currently in scope, and display a warning of some kind if such
> possibilities are found?

This is how breakpoint conditions have worked as long as I can
remember: they are evaluated at the time the breakpoint is hit,
not at the time they are typed.  So whatever they reference has
to be in scope then.

The early parsing is mainly to give early warning if something
doesn't parse.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-03-22 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22  9:40 Vladimir Prus
2008-03-22 12:07 ` Eli Zaretskii
2008-03-22 12:36   ` Vladimir Prus
2008-03-22 12:56     ` Eli Zaretskii
2008-03-22 13:20       ` Vladimir Prus
2008-03-22 14:49       ` Daniel Jacobowitz [this message]
2008-03-22 17:14         ` Eli Zaretskii
2008-03-24 18:05           ` Michael Snyder
2008-03-24 20:18             ` Eli Zaretskii
2008-03-24 21:04               ` Michael Snyder
2008-04-01 14:10 ` Daniel Jacobowitz
2008-04-03 12:51   ` Vladimir Prus
2008-04-03 13:33     ` Daniel Jacobowitz

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=20080322144931.GA19219@caradoc.them.org \
    --to=drow@false.org \
    --cc=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