From: Jonathan Wakely <jwakely@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org,
Keith Seitz <keiths@redhat.com>,
Pedro Alves <palves@redhat.com>,
gdb@sourceware.org
Subject: Re: [PATCH] PR59170 make pretty printers check for singular iterators
Date: Fri, 16 Dec 2016 13:17:00 -0000 [thread overview]
Message-ID: <20161216131732.GE895@redhat.com> (raw)
In-Reply-To: <20161216130645.GA27556@host1.jankratochvil.net>
On 16/12/16 14:06 +0100, Jan Kratochvil wrote:
>On Fri, 16 Dec 2016 13:33:52 +0100, Jonathan Wakely wrote:
>> We don't do auto-deref for std::shared_ptr or std::unique_ptr, even
>> though we know the object they point to definitely is live and safe to
>> access, and that's because those types have pointer semantics not
>> reference semantics.
>
>This is wrong std::shared_ptr or std::unique_ptr is not auto-dereferenced for
>GDB printing. But it may be more a GDB problem, not libstdc++ pretty printers
>problem.
>
>For example glib pretty printers already auto-dereference data structures:
> 5 GList* list = NULL;
> (gdb) p/r list
> $1 = (GList *) 0x607a00
> (gdb) p list
> $2 = 0x607a00 = {0x400810}
> /usr/share/glib-2.0/gdb/glib.py
> if type.code == gdb.TYPE_CODE_PTR:
> type = type.target().unqualified()
> t = str(type)
> if t == "GList":
> return GListPrinter(val, "GList")
>
>But that is more a GDB bug that should be solved even for generic pointers.
>Currently while traversing through data structures one has to randomly add or
>remove '*' from the beginning of the GDB print expression:
>
> 1 class E { int a[1000]; int i=42; } ee;
> 2 class D { E *e=ⅇ } dd;
> 3 class C { D &d=dd; } cc;
> 4 class B { C *c=&cc; } bb;
> 5 int main() {}
> (gdb) p bb
> $1 = {c = 0x601030 <cc>}
> (gdb) p bb.c
> $2 = (C *) 0x601030 <cc>
>Oops, I need to add a dereference:
> (gdb) p *bb.c
> $3 = {d = @0x601028}
> (gdb) p *bb.c.d
> No symbol "operator*" in current context.
>Oops, I need to remove a dereference:
> (gdb) p bb.c.d
> $4 = (D &) @0x601028: {e = 0x601060 <ee>}
Wat?
bb.c.d is not a valid expression.
B::c is a pointer, it should be bb.c->d
Is it GDB policy to make invalid expressions like that "work"?
Because I'm not comfortable emulating that in the libstdc++ printers.
> (gdb) p bb.c.d.e
> $5 = (E *) 0x601060 <ee>
>Oops, I need to add a dereference:
> (gdb) p *bb.c.d.e
> $6 = {a = {0 <repeats 1000 times>}, i = 42}
> (gdb) p *bb.c.d.e.i
> Cannot access memory at address 0x2a
>Oops, I need to remove a dereference:
> (gdb) p bb.c.d.e.i
> $7 = 42
I had no idea this even worked, I'd have used bb.c->d.e->i because
that's the correct expression for accessing that variable.
next prev parent reply other threads:[~2016-12-16 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161215141817.GA22699@redhat.com>
[not found] ` <20161215211903.GA22897@host1.jankratochvil.net>
[not found] ` <20161216010707.GF22266@redhat.com>
[not found] ` <20161216075136.GA21305@host1.jankratochvil.net>
[not found] ` <20161216123352.GB895@redhat.com>
2016-12-16 13:07 ` Jan Kratochvil
2016-12-16 13:17 ` Jonathan Wakely [this message]
2016-12-16 13:32 ` Jan Kratochvil
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=20161216131732.GE895@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=palves@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