This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full]
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches at sourceware dot org
- Date: Mon, 3 Oct 2011 19:43:20 +0200
- Subject: Re: [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full]
- References: <20110718201852.GG30496@host1.jankratochvil.net> <20110902170745.GA22738@host1.jankratochvil.net> <m3y5x2t3mq.fsf@fleche.redhat.com> <201110032105.17607.vladimir@codesourcery.com>
On Mon, 03 Oct 2011 19:05:17 +0200, Vladimir Prus wrote:
> 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.
I would like to restate that primarily I do not know a case when @entry values
are relevant for FEs and therefore for MI. FEs typically rebuild the inferior
for debugging with -O0 -g and therefore @entry values are not present at all.
Maybe one can use Nemiver to investigate some deployed application crash and
in such case I find @entry values important.
Regards,
Jan