Re: [MI RFC] entryval: MI access to entry values [Re: [RFC 06/12] entryval: Display @entry parameters in bt full]

André Pönitz
2011-10-10T16:09:16Z

On Monday 03 October 2011 19:43:20 ext Jan Kratochvil wrote:
> 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.

At least in "my" case libraries loaded by the inferior are often compiled
with -O2 -g, and stepping through that code is regularly done by users.

I still think it would have been nice to have a clean separation of the data
into individual "channels" on the gdb side, especially because this is new
functionality, but then, that's easily done on the FE side, too.

In any case, thank you for implementing the feature. It's much appreciated.

Andre'