Re: [PATCH] [gdb/exp] Fix printing of out of bounds struct members

[Tom Tromey <tromey@adacore.com>]

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> When building gdb with -O0 -fsanitize=address, and running test-case
Tom> gdb.ada/uninitialized_vars.exp, I run into:
Tom> ...

Thanks for looking into this.

Tom> - when y.a happens to be set to 216, as above, gdb interprets this as the
Tom>   variable having the c+d variant (which is why trying to print y.b fails).

One thing I see here is that y.a is not one of the valid values.  So I
wonder if this kind of corruption should be detected at a different
spot, like throwing an exception from compute_variant_fields_inner.

Tom> [ Given the description at the top of gdb/value.h of optimized out and
Tom> unavailable, I was not sure which one to pick for this case, so this is more
Tom> or less a random choice.

Yeah, neither seems like precisely the right fit.

Tom