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
- From: Tom Tromey <tromey at redhat dot com>
- To: Andrà PÃnitz <andre dot poenitz at nokia dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 03 Oct 2011 11:00:05 -0600
- Subject: Re: [MI RFC] entryval: MI access to entry values
- References: <20110718201852.GG30496@host1.jankratochvil.net> <201109141049.51904.andre.poenitz@nokia.com> <20110914091233.GA1328@host1.jankratochvil.net> <201109141225.56344.andre.poenitz@nokia.com>
>>>>> "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