This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] expected behavior for "bt" command used with "set language ..." ?
- From: Tom Tromey <tom at tromey dot com>
- To: Xavier Roirand <roirand at adacore dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 19 Jan 2018 13:09:31 -0700
- Subject: Re: [RFC] expected behavior for "bt" command used with "set language ..." ?
- Authentication-results: sourceware.org; auth=none
- References: <dac19f88-9639-baf1-fa19-3ae115d197a2@adacore.com>
>>>>> "Xavier" == Xavier Roirand <roirand@adacore.com> writes:
Xavier> When printing one frame arguments, should we do it using the language
Xavier> of the frame, and it may be different for each frame in a single "bt"
Xavier> command or should we leave things as they are, and possibly allow the
Xavier> "bt" command to display weird values for frame arguments or even
Xavier> worse, crash GDB because the user set language manually so he has to
Xavier> know what he's doing ?
I tend to think the answer should be:
* If the language is "auto", then use each frame's language; otherwise
* If the user specified a particular language, use that language for
everything.
Xavier> This can also probably be done by adding frame language parameter to a
Xavier> lot of language specific functions for each language and finally to
Xavier> value_cast but this second solution requires a huge amount of work.
That would be good to have but I don't think it ought to be tied to this
particular project. Certainly plenty of other code already just sets
and resets the global.
Tom