public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Alain Magloire <alain@qnx.com>
To: gdb@sources.redhat.com
Subject: RE: Failed breakpoint for C++ in gdb
Date: Thu, 28 Jul 2005 21:39:00 -0000	[thread overview]
Message-ID: <1578FF984ABAD411AFA5000102C4BB5B11DEF113@NIMBUS> (raw)



> >
> > Is the "const char *" vs. "char const *" example consistent in GDB i.e.
> can
> > I assume this and do some mangling on my own to satisfy the pickiness of
> > GDB?
> 
> This is not GDB's pickiness.

Agreed, but for the user, with code source like this foobar(const char *p);
and then having the debugger insisting on only accepting foobar(char const
*p) for breakpoint is ... heu ... bizarre.

> It is following whatever the compiler has
> specified in debug information.  You could still query GDB for the
> overloads in some fashion, I expect, but I don't know for sure.
>

That may not be possible (the query) for the front-end.  Let me ask you
rephrase the question, is this behavior dependent of the type of debug info?
i.e. if I use dwarf-2 vs. stabs++, GDB will not refuse "char const *" I can
work around this if the behavior is consistent.

Anyway, thanks for the feedback.
 

             reply	other threads:[~2005-07-28 21:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 21:39 Alain Magloire [this message]
2005-07-28 21:44 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 15:20 Alain Magloire
2005-07-29 15:29 ` Daniel Jacobowitz
2005-07-28 21:13 Alain Magloire
2005-07-28 21:16 ` Daniel Jacobowitz
2005-07-26 13:31 Alain Magloire
2005-07-26 14:01 ` 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=1578FF984ABAD411AFA5000102C4BB5B11DEF113@NIMBUS \
    --to=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).