Displaying 5 results from an estimated 5 matches for "dw_op_lit3".
2019 Nov 28
2
DW_OP_implicit_pointer design/implementation in general
...DW_AT_call_line (10)
DW_AT_call_column (0x03)
0x00000088: DW_TAG_formal_parameter
DW_AT_location (indexed (0x0) loclist = 0x00000010:
[0x00000000004004c6, 0x00000000004004d4):
DW_OP_explicit_pointer, DW_OP_lit3)
DW_AT_abstract_origin (0x00000055 "p")
------------
Please note that DW_OP_explicit_pointer denotes that following value
represents de-referenced value of optimized out pointer. With necessary
changes in LLDB debugger this dwarf info can help to detect the expl...
2019 Nov 29
4
DW_OP_implicit_pointer design/implementation in general
...DW_AT_call_column (0x03)
>>
>> 0x00000088: DW_TAG_formal_parameter
>> DW_AT_location (indexed (0x0) loclist =
>> 0x00000010:
>> [0x00000000004004c6, 0x00000000004004d4):
>> DW_OP_explicit_pointer, DW_OP_lit3)
>> DW_AT_abstract_origin (0x00000055 "p")
>> ------------
>>
>> Please note that DW_OP_explicit_pointer denotes that following value
>> represents de-referenced value of optimized out pointer. With necessary
>> changes in LLDB...
2019 Dec 18
4
DW_OP_implicit_pointer design/implementation in general
...t;>
>>>> 0x00000088: DW_TAG_formal_parameter
>>>> DW_AT_location (indexed (0x0) loclist =
>>>> 0x00000010:
>>>> [0x00000000004004c6, 0x00000000004004d4):
>>>> DW_OP_explicit_pointer, DW_OP_lit3)
>>>> DW_AT_abstract_origin (0x00000055 "p")
>>>> ------------
>>>>
>>>> Please note that DW_OP_explicit_pointer denotes that following value
>>>> represents de-referenced value of optimized out pointer....
2020 Jan 01
2
DW_OP_implicit_pointer design/implementation in general
...DW_AT_call_column (0x03)
>>
>> 0x00000088: DW_TAG_formal_parameter
>> DW_AT_location (indexed (0x0) loclist =
>> 0x00000010:
>> [0x00000000004004c6, 0x00000000004004d4):
>> DW_OP_LLVM_explicit_pointer, DW_OP_lit3) <---- in-place
>> representation of value *p=3
>> DW_AT_abstract_origin (0x00000055 "p")
>>
>> -------------------------------------------------
>> Another case you just shared can be represented using "
&...
2019 Nov 20
2
DW_OP_implicit_pointer design/implementation in general
> I don't have a strong opinion on representation. I can see how having a
dedicated instruction to model implicit pointers would aid readability & be
simpler to document/grok, but perhaps in the future we'll want to support
other operations that refer to variable > DIEs. In the short term migrating
to an extended dbg.value representation might take more work. Alok, wdyt?
Below