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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
|
Standard debugger interface
===========================
The run-time linker exposes a rendezvous structure to allow debuggers
to interface with it. This structure, r_debug, is defined in link.h.
If the executable's dynamic section has a DT_DEBUG element, the
run-time linker sets that element's value to the address where this
structure can be found.
The r_debug structure contains (amongst others) the following fields:
int r_version:
Version number for this protocol. It should be greater than 0.
struct link_map *r_map:
A linked list of loaded objects.
enum { RT_CONSISTENT, RT_ADD, RT_DELETE } r_state:
The current state of the r_map list. RT_CONSISTENT means that r_map
is not currently being modified and may safely be inspected. RT_ADD
means that an object is being added to r_map, and that the list is
not guaranteed to be consistent. Likewise RT_DELETE means that an
object is being removed from the list.
ElfW(Addr) r_brk:
The address of a function internal to the run-time linker which is
called whenever r_state is changed. The debugger should set a
breakpoint at this address if it wants to notice mapping changes.
This protocol is widely supported, but somewhat limited in that it
has no provision to provide access to multiple namespaces, and that
the notifications (via r_brk) only refer to changes to r_map--the
debugger is notified that a new object has been added, for instance,
but there is no way for the debugger to discover whether any of the
objects in the link-map have been relocated or not.
Extension to the r_debug structure
==================================
The r_debug_extended structure is an extension of the r_debug interface.
If r_version is 2, one additional field is available:
struct r_debug_extended *r_next;
Link to the next r_debug_extended structure. Each r_debug_extended
structure represents a different namespace. A namespace is active
if its r_map field isn't NULL. The first r_debug_extended structure
is for the default namespace.
Probe-based debugger interface
==============================
Systemtap is a dynamic tracing/instrumenting tool available on Linux.
Probes that are not fired at run time have close to zero overhead.
glibc contains a number of probes that debuggers can set breakpoints
on in order to notice certain events.
All rtld probes have the following arguments:
arg1: Lmid_t lmid:
The link-map ID of the link-map list that the object was loaded
into. This will be LM_ID_BASE for the application's main link-map
list, or some other value for different namespaces.
arg2: struct r_debug *r_debug:
A pointer to the r_debug structure containing the link-map list
that the object was loaded into. This will be the value stored in
DT_DEBUG for the application's main link-map list, or some other
value for different namespaces.
map_complete and reloc_complete may have the following additional
argument:
arg3: struct link_map *new:
A pointer which, if not NULL, points to the entry in the specified
r_debug structure's link-map list corresponding to the first new
object to have been mapped or relocated, with new->l_next pointing
to the link-map of the next new object to have been mapped or
relocated, and so on. Note that because `new' is an entry in a
larger list, new->l_prev (if not NULL) will point to what was the
last link-map in the link-map list prior to the new objects being
mapped or relocated.
The following probes are available:
init_start:
This is called once, when the linker is about to fill in the main
r_debug structure at application startup. init_start always has
lmid set to LM_ID_BASE and r_debug set to the value stored in
DT_DEBUG. r_debug is not guaranteed to be consistent until
init_complete is fired.
init_complete:
This is called once, when the linker has filled in the main
r_debug structure at application startup. init_complete always
has lmid set to LM_ID_BASE and r_debug set to the value stored
in DT_DEBUG. The r_debug structure is consistent and may be
inspected, and all objects in the link-map are guaranteed to
have been relocated.
map_start:
The linker is about to map new objects into the specified
namespace. The namespace's r_debug structure is not guaranteed
to be consistent until a corresponding map_complete is fired.
map_complete:
The linker has finished mapping new objects into the specified
namespace. The namespace's r_debug structure is consistent and
may be inspected, although objects in the namespace's link-map
are not guaranteed to have been relocated.
map_failed:
The linker failed while attempting to map new objects into
the specified namespace. The namespace's r_debug structure
is consistent and may be inspected.
reloc_start:
The linker is about to relocate all unrelocated objects in the
specified namespace. The namespace's r_debug structure is not
guaranteed to be consistent until a corresponding reloc_complete
is fired.
reloc_complete:
The linker has relocated all objects in the specified namespace.
The namespace's r_debug structure is consistent and may be
inspected, and all objects in the namespace's link-map are
guaranteed to have been relocated.
unmap_start:
The linker is about to remove objects from the specified
namespace. The namespace's r_debug structure is not guaranteed to
be consistent until a corresponding unmap_complete is fired.
unmap_complete:
The linker has finished removing objects into the specified
namespace. The namespace's r_debug structure is consistent and
may be inspected.
|
