public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jimb@red-bean.com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/13225] GDB fails to find non-overloaded C++ function
Date: Tue, 11 Oct 2011 19:30:00 -0000	[thread overview]
Message-ID: <bug-13225-4717-M5iuh0TYVZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13225-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=13225

--- Comment #3 from Jim Blandy <jimb@red-bean.com> 2011-10-11 19:30:21 UTC ---
Thanks for the patch, Keith!

You say:

While a real source file would require the cast, there is no reason why we
cannot be a little more permissive in the debugger.

I don't think that's correct. The transcript (with its missing newline after
the g++ command...) shows that the expression I try to evaluate in GDB is
identical to the expression appearing in the source code, which the compiler
accepts without complaint. The C++ language does not require that cast.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2011-10-11 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30  7:22 [Bug c++/13225] New: " jimb@red-bean.com
2011-10-11 18:53 ` [Bug c++/13225] " keiths at redhat dot com
2011-10-11 19:24 ` keiths at redhat dot com
2011-10-11 19:30 ` jimb@red-bean.com [this message]
2011-10-14 20:23 ` cvs-commit at gcc dot gnu.org
2011-10-14 20:24 ` cvs-commit at gcc dot gnu.org
2011-10-14 20:31 ` keiths at redhat dot com
2011-10-28 15:34 ` pedro at codesourcery dot com

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=bug-13225-4717-M5iuh0TYVZ@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).