This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [RFA] Fix breakpoint condition that use member variables.

From: Eli Zaretskii <eliz at gnu dot org>
To: Vladimir Prus <vladimir at codesourcery dot com>
Cc: gdb-patches at sources dot redhat dot com
Date: Sat, 22 Mar 2008 14:55:42 +0200
Subject: Re: [RFA] Fix breakpoint condition that use member variables.
References: <200803221240.16230.vladimir@codesourcery.com> <u8x0bgdys.fsf@gnu.org> <200803221536.07586.vladimir@codesourcery.com>
Reply-to: Eli Zaretskii <eliz at gnu dot org>

> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 22 Mar 2008 15:36:06 +0300
> Cc: gdb-patches@sources.redhat.com
> 
> > What will happen after your patch if there's also a variable i_ in
> > the selected frame?
> 
> The i_ in the breakpoint condition will be associated with the member
> variable, not with the variable with selected frame.

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?

Follow-Ups:
- Re: [RFA] Fix breakpoint condition that use member variables.
  - From: Vladimir Prus
- Re: [RFA] Fix breakpoint condition that use member variables.
  - From: Daniel Jacobowitz

References:
- [RFA] Fix breakpoint condition that use member variables.
  - From: Vladimir Prus
- Re: [RFA] Fix breakpoint condition that use member variables.
  - From: Eli Zaretskii
- Re: [RFA] Fix breakpoint condition that use member variables.
  - From: Vladimir Prus

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]