public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/13356] Be less strict about C++ overloading when calling functions from the inferior
Date: Fri, 28 Oct 2011 15:34:00 -0000 [thread overview]
Message-ID: <bug-13356-4717-3j5jKnfxpF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13356-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13356
Pedro Alves <pedro at codesourcery dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |pedro at codesourcery dot
| |com
Resolution| |DUPLICATE
--- Comment #1 from Pedro Alves <pedro at codesourcery dot com> 2011-10-28 15:33:08 UTC ---
> void foo (int *p) {}
...
> (gdb) call foo(1)
> Cannot resolve function foo to any overloaded instance
You're example passes 1, but I suspect you're not doing that in practice, but
instead, passing `0', like below, correct?
> (gdb) call foo (0)
> Cannot resolve function foo to any overloaded instance
This should work, as it is accepted by C++. Allowing any other constant is of
quite dubious value.
This is also PR13225, which is already fixed in mainline.
*** This bug has been marked as a duplicate of bug 13225 ***
--
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.
next prev parent reply other threads:[~2011-10-28 15:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 13:46 [Bug gdb/13356] New: " rguenth at gcc dot gnu.org
2011-10-28 15:34 ` pedro at codesourcery dot com [this message]
2011-10-28 15:37 ` [Bug gdb/13356] " pedro at codesourcery dot com
2011-11-02 8:35 ` rguenth at gcc dot gnu.org
2012-08-15 11:58 ` rguenther at suse dot de
2012-08-17 17:37 ` cvs-commit at gcc dot gnu.org
2012-08-17 17:40 ` keiths at redhat dot com
2013-04-25 18:36 ` keiths at redhat 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-13356-4717-3j5jKnfxpF@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).