public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/13356] New: Be less strict about C++ overloading when calling functions from the inferior Date: Fri, 28 Oct 2011 13:46:00 -0000 [thread overview] Message-ID: <bug-13356-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13356 Bug #: 13356 Summary: Be less strict about C++ overloading when calling functions from the inferior Product: gdb Version: HEAD Status: NEW Severity: enhancement Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: rguenth@gcc.gnu.org Classification: Unclassified When debugging the C++ app void foo (int *p) {} int main() {} gdb does not accept a constant as address Temporary breakpoint 1, main () at t.C:2 2 int main() {} (gdb) call foo(1) Cannot resolve function foo to any overloaded instance even though there is only a single possible overload candidate. it's annoying to figure out and paste a cast to whatever specific pointer type is required here when pasting an address from some location. gdb should be more forgiving than a C++ compiler here and do what I want. Happens a lot to me when debugging gcc built with a C++ compiler. -- 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 reply other threads:[~2011-10-28 13:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-10-28 13:46 rguenth at gcc dot gnu.org [this message] 2011-10-28 15:34 ` [Bug gdb/13356] " pedro at codesourcery dot com 2011-10-28 15:37 ` 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@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: linkBe 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).