From: Tom Tromey <tromey@redhat.com>
To: "André Pönitz" <andre.poenitz@nokia.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [MI RFC] entryval: MI access to entry values
Date: Mon, 03 Oct 2011 17:00:00 -0000 [thread overview]
Message-ID: <m3r52ut3hm.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201109141225.56344.andre.poenitz@nokia.com> (=?utf-8?Q?=22An?= =?utf-8?Q?dr=C3=A9_P=C3=B6nitz=22's?= message of "Wed, 14 Sep 2011 12:25:56 +0200")
>>>>> "André" == André Pönitz <andre.poenitz@nokia.com> writes:
Jan> There should be already instead of:
Jan> {name="lost",arg="1",value="<optimized out>"}
Jan> rather:
Jan> {name="lost",arg="1",optimized_out="1"}
André> That's actually what I'd prefer, too. No magic in-channel strings
André> that need to be recognized and handled/translated separately, but
André> different kinds of data transferred in different channels.
FWIW this makes sense to me as well.
Can you file bugs for the cases you know about? At least for this one I
think we could handle it in a backward-compatible way.
One possible issue is that the errors gdb can see are open-ended, but
presumably this could be dealt with sensibly by proper documentation.
Tom
next prev parent reply other threads:[~2011-10-03 17:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 20:21 [RFC 06/12] entryval: Display @entry parameters in bt full Jan Kratochvil
2011-07-18 22:24 ` Daniel Jacobowitz
2011-07-19 10:48 ` Eli Zaretskii
2011-07-19 10:55 ` Jan Kratochvil
2011-07-19 11:52 ` Eli Zaretskii
2011-07-19 12:17 ` Jakub Jelinek
2011-07-19 16:46 ` Eli Zaretskii
2011-07-19 17:22 ` Jakub Jelinek
2011-08-03 17:27 ` Jan Kratochvil
2011-08-03 17:53 ` Jan Kratochvil
2011-08-03 18:13 ` Jan Kratochvil
2011-08-03 18:36 ` Tom Tromey
2011-08-03 19:43 ` Jan Kratochvil
2011-09-02 17:08 ` [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full] Jan Kratochvil
2011-09-13 21:35 ` [MI RFC] entryval: MI access to entry values Jan Kratochvil
2011-09-14 8:50 ` Vladimir Prus
2011-09-14 9:13 ` André Pönitz
2011-09-14 9:20 ` Jan Kratochvil
2011-09-14 10:45 ` André Pönitz
2011-10-03 17:00 ` Tom Tromey [this message]
2011-10-03 16:57 ` [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full] Tom Tromey
2011-10-03 17:05 ` Vladimir Prus
2011-10-03 17:44 ` Jan Kratochvil
2011-10-03 18:14 ` Joel Brobecker
2011-10-10 16:09 ` André Pönitz
2011-07-19 10:57 ` [RFC 06/12] entryval: Display @entry parameters in bt full Eli Zaretskii
2011-07-19 16:21 ` Tom Tromey
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=m3r52ut3hm.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=andre.poenitz@nokia.com \
--cc=gdb-patches@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