Use allocate_optimized_out_value instead of set_value_optimized_out.
authorPedro Alves <palves@redhat.com>
Thu, 4 Jul 2013 18:10:04 +0000 (18:10 +0000)
committerPedro Alves <palves@redhat.com>
Thu, 4 Jul 2013 18:10:04 +0000 (18:10 +0000)
commit7195e6f018c7928c8b7be37e56b4df2656402618
treeb36ae6e79a2341a4e324110fe8b46527be55361e
parent58722cac5aa9ea0b18a8fe5e76031f62cea017bc
Use allocate_optimized_out_value instead of set_value_optimized_out.

Allocate the value as optimized out from the start rather than allocating
a value with contents, and then marking it optimized out.

gdb/
2013-07-04  Pedro Alves  <palves@redhat.com>

* findvar.c (value_of_register): Use allocate_optimized_out_value
if the register has been optimized out, instead of
set_value_optimized_out.
* frame-unwind.c (frame_unwind_got_optimized): Use
allocate_optimized_out_value.
gdb/ChangeLog
gdb/findvar.c
gdb/frame-unwind.c