[patch] Fix internal error on optimized-out values (regression by me)

[Jan Kratochvil]

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>

In either patch case when partially-<optimized out> values get implemented the
code needs to be changed anyway.


> and that ((struct) <optimized out>).field will need to be able to be
> <optimized out>.

Yes.


Thanks,
jan