From: Vladimir Prus <vladimir@codesourcery.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full]
Date: Mon, 03 Oct 2011 17:05:00 -0000 [thread overview]
Message-ID: <201110032105.17607.vladimir@codesourcery.com> (raw)
In-Reply-To: <m3y5x2t3mq.fsf@fleche.redhat.com>
On Monday, October 03, 2011 20:57:01 Tom Tromey wrote:
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> Jan> For (2) and (3) for FEs with proper parser an additional result
> Jan> should be ignored correctly. For FEs with some ugly manual
> Jan> matching I also do not think it should be a problem as FEs are
> Jan> usually used for -O0 -g code debugging while entry values are
> Jan> present only in -O2 -g code.
>
> For the record, I think we should not concern ourselves at all with such
> MI consumers, if any exist. MI has flaws, but this isn't among them; we
> should expect consumers to reliably ignore new fields.
I presume the question is how important those those @entry values. If this
is something that would cause user a big grief if not shown, we might just
show them in format consistent with current frontends. If that's something
nice, but not essential, than maybe 2/3 are better options.
--
Vladimir Prus
CodeSourcery / Mentor Graphics
+7 (812) 677-68-40
next prev parent reply other threads:[~2011-10-03 17:05 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
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 [this message]
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=201110032105.17607.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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