forked from ccoutant/dwarf-locations
-
Notifications
You must be signed in to change notification settings - Fork 0
/
entry-value.txt
42 lines (32 loc) · 1.68 KB
/
entry-value.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
Part 8: Clarifications for DW_OP_entry_value
This is part 8 in a series of proposals related to support for debugging
on heterogeneous architectures.
[Work in progress...]
BACKGROUND
----------
PROPOSED CHANGES
----------------
> [For further discussion, after a replacement proposal is in place...]
> In Section 2.5.1.7 Special Operations, mark DW_OP_entry_value as
> deprecated, and add the following non-normative text at the end of the
> description of DW_OP_entry_value:
>
> --------------------------------------------------------------------
> [non-normative] The DW_OP_entry_value operation is deprecated as its
> main usage is provided by other means. DWARF Version 5 added the
> DW_TAG_call_site_parameter debugger information entry for call sites
> that has DW_AT_call_value, DW_AT_call_data_location, and
> DW_AT_call_data_value attributes that provide DWARF expressions to
> compute actual parameter values at the time of the call, and
> requires the producer to ensure the expressions are valid to
> evaluate even when virtually unwound.
> --------------------------------------------------------------------
In Section 2.5.1.7 Special Operations, in the description of
DW_OP_entry_value add the following after the first paragraph:
--------------------------------------------------------------------
[non-normative] It may be used to determine the value of arguments
on entry to the current call frame provided they are not clobbered.
--------------------------------------------------------------------
> [For further discussion...]
> GDB only implements DW_OP_entry_value when E is exactly DW_OP_reg* or
> DW_OP_breg*; DW_OP_deref*.