Re: Failed breakpoint for C++ in gdb

Daniel Jacobowitz
2005-07-26T14:01:38Z

On Tue, Jul 26, 2005 at 09:31:10AM -0400, Alain Magloire wrote:
> Why is gdb so fussy about the argument order ?

GDB generally matches the compiler-generated debug info. There's a
long-term plan to be more forgiving about this, but it's hard to
implement that without slowing down symbol reading...

> (gdb) b foo(const char *)
> Function "foo(const char *)" not defined
> (gdb) b foo(char const *)
> Breakpoint 1 at 0x....... file testing.cpp line 4.
>
> So is there something I should do ? Do I have to reorder my arguments to put
> the const last ?

Is this for command line use? Try: b 'foo<TAB>