Re: [PATCH 1/1] gdb: Handle TYPE_CODE_COMPLEX in valprint_check_validity.

[Tom Tromey <tom@tromey.com>]

>>>>> Abdul Basit Ijaz <abdul.b.ijaz@intel.com> writes:

> The issue occurred because valprint_check_validity () only exempted
> TYPE_CODE_UNION, TYPE_CODE_STRUCT, and TYPE_CODE_ARRAY from the
> optimized-out check, but not TYPE_CODE_COMPLEX.  Complex types, like
> structures, can have components with different availability.

Thanks for the patch.

I wouldn't be surprised if there are other places that check for
"aggregate" types and overlook the complex number case.

> +			DW_OP_implicit_value 0x00 0x00 0x40 0x40

I guess it's possible that this will be something strange on some
system, one with a weird floating point encoding.  However I think it's
fine not to worry about it for now.

> +gdb_test "print z1" "= \[0-9\]+ \\+ <optimized out>i" \

Just as an aside, this is the kind of thing that quotemeta makes nicer,
like

    [quotemeta " = @DECIMAL + <optimized out>i"]

But anyway what you have is also fine.

Approved-By: Tom Tromey <tom@tromey.com>

Tom