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:37:00 -0000	[thread overview]
Message-ID: <bug-13356-4717-9VCcMg3Q2x@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|RESOLVED                    |REOPENED
         Resolution|DUPLICATE                   |

--- Comment #2 from Pedro Alves <pedro at codesourcery dot com> 2011-10-28 15:36:41 UTC ---
> 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.

Bah, sorry I need to learn to read.

I'd be happier if gdb accepted (void*) instead of random integers though. 
Maybe this should be an option.

-- 
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-28 15:37 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 [this message]
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-9VCcMg3Q2x@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).