From: Tom Tromey <tromey@redhat.com>
To: "Elmenthaler\, Jens" <jens.elmenthaler@verigy.com>
Cc: <gdb@sourceware.org>
Subject: Re: [Pretty printers] Can the name or type of a child value change?
Date: Mon, 16 Aug 2010 20:53:00 -0000 [thread overview]
Message-ID: <m3vd7al1ns.fsf@fleche.redhat.com> (raw)
In-Reply-To: <58596C4646708B4BB990C4483997333002F403D9@usplmvpbe001.ent.rt.verigy.net> (Jens Elmenthaler's message of "Fri, 13 Aug 2010 01:41:05 -0500")
>>>>> "Jens" == Elmenthaler, Jens <jens.elmenthaler@verigy.com> writes:
Jens> Consider the following code example:
[...]
Jens> When stepping in the debugger over a line that changes JAny.type,
Jens> the name and the type of the child value returned by the pretty
Jens> printer change.
Jens> Are the MI variable objects meant to handle this?
Yes. The MI consumer is expected to understand that dynamic varobjs are
dynamic: the number and names of children can change in arbitrary ways.
This is incompatible with previous expectations, which is why consumers
have to explicitly request this feature from gdb.
Tom
next prev parent reply other threads:[~2010-08-16 20:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 6:41 Elmenthaler, Jens
2010-08-16 20:53 ` Tom Tromey [this message]
2012-03-28 8:03 ` Elmenthaler, Jens
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=m3vd7al1ns.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=jens.elmenthaler@verigy.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).