Re: gdb needs full C++ function signature to set a breakpoint

Daniel Jacobowitz
2005-07-08T14:19:07Z

On Fri, Jul 08, 2005 at 04:09:44PM +0200, Klaus Zeitler wrote:
> I figured out the difference between my small example and the big image.
> For the example image gdb correctly recognizes the program as C++, i.e. says:
> "The current source language is "auto; currently c++"."
> whereas for the real image gdb claims, that it's c.
> So a simple "set lang c++" is all that was needed.
>
> Now I would like to know why gdb thinks that this is a c image.
> Could it be that gdb decides that by searching main()?

GDB does not have a single impression of the language - it depends on
the current location in the code. But yes, before the program is
started, the current "location" used is main().

This is a wart; it'd be nice if the CLI did not depend on this for some
things that it does presently, but it isn't clear how to fix it.

--
Daniel Jacobowitz
CodeSourcery, LLC