Re: [RFC/RFA?] Should break FILE:LINENO skip prologue?

[Eli Zaretskii <eliz at gnu dot org>]

> Date: Wed, 16 Jan 2008 11:34:41 +0100 (CET)
> From: Mark Kettenis <mark.kettenis@xs4all.nl>
> CC: uweigand@de.ibm.com, brobecker@adacore.com, msnyder@specifix.com,
>         gdb-patches@sourceware.org
> 
> > Btw, the manual does not say *EXPRESSION, it says *ADDRESS.
> 
> That's fine as long as the manual says that ADDRESS is parsed as an
> expression in the current language.

It doesn't.  It says it "may be any expression", which is vague, even
inaccurate.

> > Anyway, if "break *FILENAME:FUNCTION" does not need to work, then how
> > does one set a breakpoint on the entry point of FILENAME:FUNCTION,
> > after the suggested change that makes "break FUNCTION" behave
> > differently than "break *FUNCTION"?
> 
> Joel's change does not change how "break FUNCTION" works at all.  It
> changes what "break LINE" does in the case where LINE doesn't
> correspond to an actual line of source code, and makes it more similar
> to what "break FUNCTION" does, which is putting the breakpoint on the
> first line of actual code in a function.

My question was about putting the breakpoint on the beginning of the
prolog of a function in another file, not about "break FUNCTION" or
"break LINE".  You didn't answer my question: how does one put a
breakpoint on that address.  For a function in the current file, or
one whose name identifies it unambiguously, "break *FUNCTION" is the
solution.  But what about the case where FUNCTION alone is not enough
to unambiguously specify a function?