forked from aaronbloomfield/pdr
-
Notifications
You must be signed in to change notification settings - Fork 228
/
lldb_summary.html
116 lines (116 loc) · 5.37 KB
/
lldb_summary.html
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
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
<head>
<meta charset="utf-8" />
<meta name="generator" content="pandoc" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
<title>PDR: Docs: LLDB Command Summary</title>
<style>
code{white-space: pre-wrap;}
span.smallcaps{font-variant: small-caps;}
span.underline{text-decoration: underline;}
div.column{display: inline-block; vertical-align: top; width: 50%;}
div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;}
ul.task-list{list-style: none;}
.display.math{display: block; text-align: center; margin: 0.5rem auto;}
</style>
<link rel="stylesheet" href="../markdown.css" />
<!--[if lt IE 9]>
<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7.3/html5shiv-printshiv.min.js"></script>
<![endif]-->
</head>
<body>
<h1 id="pdr-docs-lldb-command-summary">PDR: Docs: LLDB Command
Summary</h1>
<p><a href="index.html">Go up to the main documents page</a> (<a
href="index.md">md</a>)</p>
<p>Assembly-specific commands</p>
<ul>
<li><code>stepi</code>: step one MACHINE instruction (i.e. assembly
instruction), instead of one C++ instruction (which is what
<code>step</code> does)</li>
<li><code>register read</code>: display the values in the registers</li>
<li><code>settings set target.x86-disassembly-flavor intel</code>: set
the assembly output format to what we are used to in class (and what we
are programming in)</li>
<li><code>disassemble</code>: like list, but displays the lines of
assembly code currently being executed.</li>
<li><code>disassemble --name (function)</code>: prints the assembly code
for the supplied function (up until the next label)</li>
</ul>
<p>Program execution</p>
<ul>
<li><code>run</code>: starts a program execution, and continues until it
exits, crashes, or hits a breakpoint</li>
<li><code>bt</code>: prints a back trace, which is the list of function
calls that got to the current point</li>
<li><code>f</code>: shows the lines of source code before and after the
point at which the program paused</li>
<li><code>list (function)</code>: prints the lines of code around
(function) or the current breakpoint otherwise if no (function) is
provided.</li>
<li><code>up</code>: move up the back trace function stack list</li>
<li><code>down</code>: move down the back trace function stack list</li>
<li><code>step</code> (or just <code>s</code>): step INTO the next line
of code to execute</li>
<li><code>next</code> (or just <code>n</code>): step OVER the next line
of code to execute</li>
<li><code>continue</code> (or just <code>c</code>): continue
execution</li>
<li><code>finish</code>: finishes executing the current function and
then pauses</li>
<li><code>quit</code>: exits the debugger</li>
</ul>
<p>Breakpoints</p>
<ul>
<li><code>b (pos)</code> (or <code>break (pos)</code>): set a breakpoint
at (pos). A breakpoint can be a function name (e.g., <code>b
GetMax</code>), a line number (e.g., <code>b 22</code>), or either of
the above preceded by a file name (e.g., <code>b lab2.cpp:22</code> or
<code>b lab2.cpp:GetMax</code>)</li>
<li><code>tbreak (pos)</code>: set a temporary breakpoint (only breaks
the first time)</li>
<li><code>breakpoint list</code>: show breakpoints</li>
<li><code>breakpoint delete</code> (or just <code>br del</code>):
deletes all breakpoints</li>
<li><code>breakpoint delete (num)</code>: delete the breakpoint
indicated by (num)</li>
</ul>
<p>Examining data</p>
<ul>
<li><code>print (var)</code> (or <code>p</code>): print the value in the
given variable</li>
<li><code>print &(var)</code>: print the address that the given
variable is located</li>
<li><code>print *(ptr)</code>: print the destination of a pointer</li>
<li><code>x/(format) (var/address)</code>: format controls how the
memory should be displayed, and consists of (up to) 3 components: a
numeric count of how many elements to display; a single-character
format, indicating how to interpret and display each element – e.g. a
few of the flags are <code>x/x</code> displays in hex, <code>x/d</code>
displays in signed decimals, <code>x/c</code> displays in characters,
<code>x/i</code> displays in instructions, and <code>x/s</code> displays
in C strings; and a single-character size, indicating the size of each
element to display – e.g. b, h, w, and g, for one-, two-, four-, and
eight-byte blocks, respectively. You can have multiple at a time,
e.g. <code>x/30x (var/address)</code> will display 30 elements in
hexidecimal from the provided <code>var/address</code> OR if no
<code>var/address</code> is provided, from the top of the stack.</li>
<li><code>frame variable</code>: display all the args and the local
variables and their values for their current frame</li>
<li><code>display (var)</code>: always display the value in (var)
whenever the program pauses</li>
<li><code>display</code>: show the variables that have been entered with
<code>display</code> and their numeric IDs</li>
<li><code>undisplay (num)</code>: stop displaying the variable with
numeric ID num</li>
<li><code>print function_call(params)</code>: execute the function, and
print the result</li>
<li><code>expr (var) = (value)</code>: set the variable (var) to the
value (value) – e.g. <code>expr foo = 5</code></li>
<li><code>up</code> and <code>down</code>: moves up a frame or down a
frame in the backtrace (<code>bt</code>) of a crashed or paused
program</li>
</ul>
</body>
</html>