From: Mike Stump <mikestump@comcast.net>
To: Diego Novillo <dnovillo@google.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Lawrence Crowl <crowl@google.com>,
Paolo Bonzini <bonzini@gnu.org>, DJ Delorie <dj@redhat.com>,
Tom Tromey <tromey@redhat.com>,
Laurynas Biveinis <laurynas.biveinis@gmail.com>,
gdb@sourceware.org, Richard Guenther <rguenther@suse.de>
Subject: Re: Merge C++ conversion into trunk (0/6 - Overview)
Date: Wed, 15 Aug 2012 14:25:00 -0000 [thread overview]
Message-ID: <180D8A6D-B325-4CFE-811B-F09A23FF2E7A@comcast.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1208151357110.28649@zhemvz.fhfr.qr>
On Aug 15, 2012, at 4:59 AM, Richard Guenther wrote:
> and debugging becomes a nightmare (hello gdb people!)
> (gdb) call debug_tree (0x7ffff67fa5e8)
> Cannot resolve function debug_tree to any overloaded instance
Inquiring minds want to know if:
macro define debug_tree(A) ((tree)A)
makes the above work if you put it into gdbinit.in? If yes, then, I think for now we should add such lines for every non-overloaded function, I too like using hex constants from dumps. Oh, or, maybe we just add a debug_tree(long) overload just to satisfy gdb.
prev parent reply other threads:[~2012-08-15 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120812200427.GA12561@google.com>
2012-08-15 12:01 ` Richard Guenther
2012-08-15 12:19 ` Diego Novillo
2012-08-15 12:21 ` Richard Guenther
2012-08-15 12:23 ` Diego Novillo
2012-08-15 15:13 ` Jan Kratochvil
2012-08-15 15:44 ` Michael Matz
2012-08-15 15:50 ` Jan Kratochvil
2012-08-15 16:39 ` Jakub Jelinek
2012-08-15 16:00 ` Diego Novillo
2012-08-15 17:54 ` Tom Tromey
2012-08-15 18:02 ` Gabriel Dos Reis
2012-08-15 18:21 ` Tom Tromey
2012-08-15 18:26 ` Gabriel Dos Reis
2012-08-17 17:45 ` Keith Seitz
2012-08-17 17:56 ` H.J. Lu
2012-08-15 14:25 ` Mike Stump [this message]
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=180D8A6D-B325-4CFE-811B-F09A23FF2E7A@comcast.net \
--to=mikestump@comcast.net \
--cc=bonzini@gnu.org \
--cc=crowl@google.com \
--cc=dj@redhat.com \
--cc=dnovillo@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=laurynas.biveinis@gmail.com \
--cc=rguenther@suse.de \
--cc=tromey@redhat.com \
/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).