This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Consistent display of "<optimized out>"
- From: "Andrew Burgess" <aburgess at broadcom dot com>
- To: gdb-patches at sourceware dot org
- Cc: "Pedro Alves" <palves at redhat dot com>, "Mark Kettenis" <mark dot kettenis at xs4all dot nl>
- Date: Mon, 12 Aug 2013 14:31:52 +0100
- Subject: Re: [PATCH] Consistent display of "<optimized out>"
- References: <5200F55E dot 2050308 at broadcom dot com> <201308061318 dot r76DIMdd016369 at glazunov dot sibelius dot xs4all dot nl> <5200FECF dot 7030304 at broadcom dot com> <201308061541 dot r76FfYQN022875 at glazunov dot sibelius dot xs4all dot nl> <520142D9 dot 4030304 at redhat dot com>
On 06/08/2013 7:39 PM, Pedro Alves wrote:
> On 08/06/2013 04:41 PM, Mark Kettenis wrote:
>>> Date: Tue, 6 Aug 2013 14:49:03 +0100
>>> From: "Andrew Burgess" <aburgess@broadcom.com>
>
>>> 3. My understanding was that values lost due to the ABI of a call site
>>> were recorded as optimized out. For evidence I would present
>>> dwarf2_frame_prev_register, and how DWARF2_FRAME_REG_UNDEFINED is handled.
>>>
>>> For these reasons I believe my patch should still be considered, what do
>>> you think?
>>
>> I think that registers are either available or unavailble. A register
>> being unavailble implies that a variable that is supposed to live in
>> such a register may have been optimized out. Whether GDB's pseudo
>> variables that respresent registers are considered unavailable or
>> optimized out in that case is arguable.
>
> I think improving consistency as in Andrew's patch is good.
Given almost a week has passed with no further feedback I plan to
commit this patch tomorrow unless there's any further discussion to be had.
Thanks,
Andrew