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: Tom Tromey <tromey at redhat dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: Vladimir Prus <vladimir at codesourcery dot com>, gdb-patches at sourceware dot org
- Date: Mon, 03 Oct 2011 10:57:01 -0600
- 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> <CAN9gPaFFbEXH373MfCsS_LQga65X4VT9T57KnFgXOxpmmGih4g@mail.gmail.com> <20110902170745.GA22738@host1.jankratochvil.net>
>>>>> "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.
Tom