This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: error reading variable: value has been optimized out


>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Andrew> Looking through, value.c is seems there might also support for
Andrew> having values partially optimised out, this would seem like a
Andrew> better solution, but I'm not sure the right way to hook this in,
Andrew> if anyone would like to offer suggestions I'm happy to create a
Andrew> new patch, alternatively, this could be improved on later...

Jan> GDB supports partially unavailable values from partially stored traces.
Jan> This is AFAIK not applicable for partially optimized out values.

I'm not sure whether I'm understanding your comment correctly, but gdb
does support partially optimized out values.  However, these are only
supported for lval_computed values.  See lval_funcs::check_validity and
check_any_valid.

Offhand it seems as though read_frame_register_value could create an
lval_computed value if any register it needs is optimized out.  I don't
know whether this is worth the effort.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]