This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: rules for conditional breakpoints
- From: Jim Blandy <jimb at redhat dot com>
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Cc: Peter Jay Salzman <p at dirac dot org>, Gdb Mailing List <gdb at sources dot redhat dot com>
- Date: 26 Sep 2002 15:39:41 -0500
- Subject: Re: rules for conditional breakpoints
- References: <Pine.SUN.3.91.1020926075004.12918I@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On Wed, 25 Sep 2002, Peter Jay Salzman wrote:
>
> > what exactly are the rules for conditional breakpoints?
>
> If that's not clear from reading the manual, I think we should fix the
> manual.
The expressions allowed in conditional breakpoints are exactly those
allowed in "print". Peter assumed that the restriction had something
to do with conditional breakpoints, but that's not so. The manual's
description of conditional breakpoints is perfectly clear.
What should be clarified, I think, is the description of expressions.
I seem to remember issues like this having come up before. I'd
suggest putting a clarification in ``Expressions'', pointing out that,
while GDB *can* reference variables and call functions for which it
has no debug info, it assumes they're `int' and `int () (int)'. When
that's wrong, one should expect the ensuing problems.
I'm too drowsy to suggest any decent wording at the moment. Sorry.