This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Fix internal error on optimized-out values (regression by me)
- From: Pedro Alves <pedro at codesourcery dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: gdb-patches at sourceware dot org, Tom Tromey <tromey at redhat dot com>
- Date: Thu, 13 Oct 2011 16:27:34 +0100
- Subject: Re: [patch] Fix internal error on optimized-out values (regression by me)
- References: <20110926191132.GA30401@host1.jankratochvil.net> <201110102240.28440.pedro@codesourcery.com> <20111012203329.GA23721@host1.jankratochvil.net>
On Wednesday 12 October 2011 21:33:29, Jan Kratochvil wrote:
> On Mon, 10 Oct 2011 23:40:28 +0200, Pedro Alves wrote:
> > IMO, this is just like "p s.f", printing <unavailable> when the whole
> > of `s' is unavailable. From the unavailable.exp test:
> >
> > print globalstruct.memberf
> > $7 = <unavailable>
> > (gdb) PASS: gdb.trace/unavailable.exp: collect globals: print globalstruct.memberf
> > print globalstruct.memberd
> > print globalstruct
> > $9 = {memberc = <unavailable>, memberi = <unavailable>, memberf = <unavailable>, memberd = <unavailable>}
> >
> > It just happens that today, we only support either wholy
> > optimized-out values, or wholly not optimized-out values.
>
> This would suggest the user-visible behavior should be more the former patch:
> http://sourceware.org/ml/gdb-patches/2011-09/msg00449.html
> printing <optimized out>
Yes.
--
Pedro Alves