public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "keiths at redhat 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, 17 Aug 2012 17:40:00 -0000 [thread overview] Message-ID: <bug-13356-4717-5KDj500smD@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-13356-4717@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=13356 Keith Seitz <keiths at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED CC| |keiths at redhat dot com Resolution| |FIXED AssignedTo|unassigned at sourceware |keiths at redhat dot com |dot org | Target Milestone|--- |7.6 --- Comment #6 from Keith Seitz <keiths at redhat dot com> 2012-08-17 17:40:11 UTC --- I have committed a patchset to fix this. [Note the patchset is large because it contains a large cleanup of dead code.] Please let me know if there are any further issues. -- 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:[~2012-08-17 17:40 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 ` [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 [this message] 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-5KDj500smD@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).