From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Diego Novillo <dnovillo@google.com>
Cc: Richard Guenther <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Lawrence Crowl <crowl@google.com>,
bonzini@gnu.org, dj@redhat.com, tromey@redhat.com,
laurynas.biveinis@gmail.com, gdb@sourceware.org
Subject: Re: Merge C++ conversion into trunk (0/6 - Overview)
Date: Wed, 15 Aug 2012 15:13:00 -0000 [thread overview]
Message-ID: <20120815151227.GA1324@host2.jankratochvil.net> (raw)
In-Reply-To: <502B94C9.4020607@google.com>
On Wed, 15 Aug 2012 14:23:37 +0200, Diego Novillo wrote:
> GDB folks, would it be hard to figure out that there is a single
> variant of the called function and trust the user that they are
> passing the right pointer value?
It is a needless violation of C++ resolving rules. There are various easy way
how to get it working (in .gdbinit or cc1-gdb.gdb define GDB function, define
macro in GDB, use GDB python pretty printer instead (possibly even calling GCC
inferior function) etc.).
While I did not post such patch yet I would prefer to even forbid by default
expressions like
(gdb) print *0x1234567
and enforce
(gdb) print *(int *)0x1234567
instead as the former syntax confuses people (as commonly seen on IRC), the
same applies to calling functions without full debuginfo (they should require
an explicit cast in GDB) etc.
Regards,
Jan
next prev parent reply other threads:[~2012-08-15 15:13 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 [this message]
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
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=20120815151227.GA1324@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--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).