From: Daniel Jacobowitz <drow@false.org>
To: Alain Magloire <alain@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: Failed breakpoint for C++ in gdb
Date: Tue, 26 Jul 2005 14:01:00 -0000 [thread overview]
Message-ID: <20050726140129.GA6826@nevyn.them.org> (raw)
In-Reply-To: <1578FF984ABAD411AFA5000102C4BB5B11DEEB0C@NIMBUS>
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>
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-26 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 13:31 Alain Magloire
2005-07-26 14:01 ` Daniel Jacobowitz [this message]
2005-07-28 21:13 Alain Magloire
2005-07-28 21:16 ` Daniel Jacobowitz
2005-07-28 21:39 Alain Magloire
2005-07-28 21:44 ` Daniel Jacobowitz
2005-07-29 15:20 Alain Magloire
2005-07-29 15:29 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050726140129.GA6826@nevyn.them.org \
--to=drow@false.org \
--cc=alain@qnx.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).