maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/lldb/www/lldb-gdb.html

1070 lines
48 KiB
HTML
Raw Normal View History

Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link href="style.css" rel="stylesheet" type="text/css" />
Fix <title> on webpage. llvm-svn: 146085
2011-12-08 06:09:43 +08:00
<title>LLDB to GDB Command Map</title>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</head>
<body>
<div class="www_title">
The <strong>LLDB</strong> Debugger
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<div id="container">
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div id="content">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<!--#include virtual="sidebar.incl"-->
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div id="middle">
<div class="post">
one more small fix for the gdb-comes-first column order llvm-svn: 165301
2012-10-05 13:31:01 +08:00
<h1 class ="postheader">GDB to LLDB Command Map</h1>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div class="post">
Update the intro paragraph of text describing the table below to reflect that the columns were just swapped. llvm-svn: 165295
2012-10-05 12:28:33 +08:00
<p>Below is a table of GDB commands with the LLDB counterparts.
Fixing a typo in the lldb-gdb webpage llvm-svn: 156779
2012-05-15 05:39:38 +08:00
The built in GDB-compatibility aliases in LLDB are also
Update the intro paragraph of text describing the table below to reflect that the columns were just swapped. llvm-svn: 165295
2012-10-05 12:28:33 +08:00
listed. The full lldb command names are often long, but any
typeo llvm-svn: 165297
2012-10-05 12:29:13 +08:00
unique short form can be used. Instead of "<b>breakpoint set</b>",
"<b>br se</b>" is also acceptable.</p>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div class="postfooter"></div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<h1 class ="postheader">Execution Commands</h1>
<div class="post">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<p>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<table class="stats" width="620" cellspacing="0">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Launch a process no arguments.</td></tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> run<br>
<b>(gdb)</b> r
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> process launch<br>
<b>(lldb)</b> run<br>
<b>(lldb)</b> r
</td>
</tr>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Launch a process with arguments <code>&lt;args&gt;</code>.</td></tr>
<td class="content">
<b>(gdb)</b> run &lt;args&gt;<br>
<b>(gdb)</b> r &lt;args&gt;
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> process launch -- &lt;args&gt;<br>
<b>(lldb)</b> r &lt;args&gt;
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Launch a process for with arguments <b><code>a.out 1 2 3</code></b> without having to supply the args every time.</td></tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>%</b> gdb --args a.out 1 2 3<br>
<b>(gdb)</b> run<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
...<br>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> run<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
...<br>
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>%</b> lldb -- a.out 1 2 3<br>
<b>(lldb)</b> run<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
...<br>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> run<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
...<br>
</td>
</tr>
<tr><td class="header" colspan="2">Launch a process with arguments in new terminal window (Mac OS X only).</td></tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> process launch --tty -- &lt;args&gt;<br>
<b>(lldb)</b> pro la -t -- &lt;args&gt;<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Launch a process with arguments in existing terminal <cope>/dev/ttys006</code> (Mac OS X only).</td></tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> process launch --tty=/dev/ttys006 -- &lt;args&gt;<br>
<b>(lldb)</b> pro la -t/dev/ttys006 -- &lt;args&gt;<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Attach to a process with process ID 123.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> attach 123
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> process attach --pid 123<br>
<b>(lldb)</b> attach -p 123
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Attach to a process named "a.out".</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> attach a.out
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> process attach --name a.out<br>
<b>(lldb)</b> pro at -n a.out
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Wait for a process named "a.out" to launch and attach.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> attach -waitfor a.out
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> process attach --name a.out --waitfor<br>
<b>(lldb)</b> pro at -n a.out -w
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
<tr><td class="header" colspan="2">Attach to a remote gdb protocol server running on system "eorgadd", port 8000.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> target remote eorgadd:8000
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> gdb-remote eorgadd:8000
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Attach to a remote gdb protocol server running on the local system, port 8000.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> target remote localhost:8000
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> gdb-remote 8000
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Attach to a Darwin kernel in kdp mode on system "eorgadd".</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> kdp-reattach eorgadd
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> kdp-remote eorgadd
Add examples of using the kdp-remote and gdb-remote commands to connect to gdb-remote protocol and kdp protocol systems. llvm-svn: 164730
2012-09-27 06:42:25 +08:00
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Do a source level single step in the currently selected thread.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> step<br>
<b>(gdb)</b> s
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> thread step-in<br>
<b>(lldb)</b> step<br>
<b>(lldb)</b> s
</td>
</tr>
<tr><td class="header" colspan="2">Do a source level single step over in the currently selected thread.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> next<br>
<b>(gdb)</b> n
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> thread step-over<br>
<b>(lldb)</b> next<br>
<b>(lldb)</b> n<br>
</td>
</tr>
<tr><td class="header" colspan="2">Do an instruction level single step in the currently selected thread.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> stepi<br>
<b>(gdb)</b> si
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> thread step-inst<br>
<b>(lldb)</b> si<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Do an instruction level single step over in the currently selected thread.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> nexti<br>
<b>(gdb)</b> ni
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> thread step-inst-over<br>
<b>(lldb)</b> ni
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Step out of the currently selected frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> finish<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> thread step-out<br>
<b>(lldb)</b> finish<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Backtrace and disassemble every time you stop.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
</td>
<td class="content">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<b>(lldb)</b> target stop-hook add<br>
Enter your stop hook command(s). Type 'DONE' to end.<br>
&gt; bt<br>
&gt; disassemble --pc<br>
&gt; DONE<br>
Stop hook #1 added.<br>
</td>
</tr>
</table>
<p>
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div class="postfooter"></div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<h1 class ="postheader">Breakpoint Commands</h1>
<div class="post">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<p>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<table class="stats" width="620" cellspacing="0">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Set a breakpoint at all functions named <b>main</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> break main
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> breakpoint set --name main<br>
<b>(lldb)</b> br s -n main<br>
<b>(lldb)</b> b main
</td>
</tr>
<tr><td class="header" colspan="2">Set a breakpoint in file <b>test.c</b> at line <b>12</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> break test.c:12
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> breakpoint set --file test.c --line 12<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> br s -f test.c -l 12<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<b>(lldb)</b> b test.c:12
</td>
</tr>
<tr><td class="header" colspan="2">Set a breakpoint at all C++ methods whose basename is <b>main</b>.</td></tr>
<tr>
<td class="content">
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(gdb)</b> break main<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<i>(Hope that there are no C funtions named <b>main</b>)</i>.
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> breakpoint set --method main<br>
<b>(lldb)</b> br s -M main<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<tr><td class="header" colspan="2">Set a breakpoint at and object C function: <b>-[NSString stringWithFormat:]</b>.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> break -[NSString stringWithFormat:]<br>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> breakpoint set --name "-[NSString stringWithFormat:]"<br>
<b>(lldb)</b> b -[NSString stringWithFormat:]<br>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Set a breakpoint at all Objective C methods whose selector is <b>count</b>.</td></tr>
<tr>
<td class="content">
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(gdb)</b> break count<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<i>(Hope that there are no C or C++ funtions named <b>count</b>)</i>.
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> breakpoint set --selector count<br>
<b>(lldb)</b> br s -S count<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
Mention "break set -r" and "break set -p". llvm-svn: 166238
2012-10-19 05:54:05 +08:00
<tr><td class="header" colspan="2">Set a breakpoint by regular expression on function name.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> rbreak regular-expression<br>
</td>
<td class="content">
<b>(lldb)</b> breakpoint set --regex regular-expression<br>
<b>(lldb)</b> br s -r regular-expression<br>
</td>
</tr>
<tr><td class="header" colspan="2">Set a breakpoint by regular expression on source file contents.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> shell grep -e -n pattern source-file<br>
<b>(gdb)</b> break source-file:CopyLineNumbers<br>
</td>
<td class="content">
<b>(lldb)</b> breakpoint set --source-pattern regular-expression --file SourceFile<br>
<b>(lldb)</b> br s -p regular-expression -f file<br>
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
Added examples of commands that list and delete breakpoints. llvm-svn: 147549
2012-01-05 05:20:39 +08:00
<tr><td class="header" colspan="2">List all breakpoints.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info break<br>
Added examples of commands that list and delete breakpoints. llvm-svn: 147549
2012-01-05 05:20:39 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> breakpoint list<br>
<b>(lldb)</b> br l<br>
Added examples of commands that list and delete breakpoints. llvm-svn: 147549
2012-01-05 05:20:39 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Delete a breakpoint.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> delete 1<br>
Added examples of commands that list and delete breakpoints. llvm-svn: 147549
2012-01-05 05:20:39 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> breakpoint delete 1<br>
<b>(lldb)</b> br del 1<br>
Added examples of commands that list and delete breakpoints. llvm-svn: 147549
2012-01-05 05:20:39 +08:00
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</table>
<p>
</div>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
<div class="postfooter"></div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
<h1 class ="postheader">Watchpoint Commands</h1>
<div class="post">
<p>
<table class="stats" width="620" cellspacing="0">
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</tr>
<tr><td class="header" colspan="2">Set a watchpoint on a variable when it is written to.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> watch global_var
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
<td class="content">
Improve shortened examples of the watchpoint commands. Document "f <n>" selects frame n. "t <n>" selects thread n but this was just added to TOT so most people won't have access to an lldb that accepts it. llvm-svn: 165332
2012-10-06 04:25:53 +08:00
<b>(lldb)</b> watchpoint set variable global_var<br>
<b>(lldb)</b> wa s v global_var<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Set a watchpoint on a memory location when it is written into. The size of the region to watch for defaults to the pointer size if no '-x byte_size' is specified.
This command takes raw input, evaluated as an expression returning an unsigned integer pointing to the start of the region, after the '--' option terminator.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> watch -location g_char_ptr
</td>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
<td class="content">
Remove two more cases of "-w write" being specified to watch var set/exp -- that's now the default in the shipped lldb. llvm-svn: 165333
2012-10-06 04:28:11 +08:00
<b>(lldb)</b> watchpoint set expression -- my_ptr<br>
Improve shortened examples of the watchpoint commands. Document "f <n>" selects frame n. "t <n>" selects thread n but this was just added to TOT so most people won't have access to an lldb that accepts it. llvm-svn: 165332
2012-10-06 04:25:53 +08:00
<b>(lldb)</b> wa s e -- my_ptr<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Set a condition on a watchpoint</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
</td>
<td class="content">
Remove two more cases of "-w write" being specified to watch var set/exp -- that's now the default in the shipped lldb. llvm-svn: 165333
2012-10-06 04:28:11 +08:00
<b>(lldb)</b> watch set var global<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
<b>(lldb)</b> watchpoint modify -c '(global==5)'<br>
<b>(lldb)</b> c<br>
...<br>
<b>(lldb)</b> bt<br>
* thread #1: tid = 0x1c03, 0x0000000100000ef5 a.out`modify + 21 at main.cpp:16, stop reason = watchpoint 1<br>
frame #0: 0x0000000100000ef5 a.out`modify + 21 at main.cpp:16<br>
frame #1: 0x0000000100000eac a.out`main + 108 at main.cpp:25<br>
frame #2: 0x00007fff8ac9c7e1 libdyld.dylib`start + 1<br>
<b>(lldb)</b> frame var global<br>
(int32_t) global = 5<br>
</td>
</tr>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
<tr><td class="header" colspan="2">List all watchpoints.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info break<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> watchpoint list<br>
<b>(lldb)</b> watch l<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Delete a watchpoint.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> delete 1<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> watchpoint delete 1<br>
<b>(lldb)</b> watch del 1<br>
rdar://problem/11057400 Add documentation for watchpoint commands. llvm-svn: 152882
2012-03-16 08:44:02 +08:00
</td>
</tr>
</table>
<p>
</div>
<div class="postfooter"></div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<h1 class ="postheader">Examining Variables</h1>
<div class="post">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<p>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<table class="stats" width="620" cellspacing="0">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Show the arguments and local variables for the current frame.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> info args<br>
and<br>
<b>(gdb)</b> info locals<br>
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> frame variable<br>
Improve shortened examples of the watchpoint commands. Document "f <n>" selects frame n. "t <n>" selects thread n but this was just added to TOT so most people won't have access to an lldb that accepts it. llvm-svn: 165332
2012-10-06 04:25:53 +08:00
<b>(lldb)</b> fr v<br>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<tr><td class="header" colspan="2">Show the local variables for the current frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info locals<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> frame variable --no-args<br>
<b>(lldb)</b> fr v -a<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the contents of local variable "bar".</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> p bar<br>
</td>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<td class="content">
<b>(lldb)</b> frame variable bar <br>
<b>(lldb)</b> fr v bar <br>
<b>(lldb)</b> p bar <br>
</td>
</tr>
<tr><td class="header" colspan="2">Show the contents of local variable "bar" formatted as hex.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> p/x bar<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> frame variable --format x bar <br>
<b>(lldb)</b> fr v -f x bar <br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the contents of global variable "baz".</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> p baz<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> target variable baz <br>
<b>(lldb)</b> ta v baz <br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the global/static variables defined in the current source file.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
n/a<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> target variable <br>
<b>(lldb)</b> ta v <br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</td>
</tr>
typeo llvm-svn: 142900
2011-10-25 09:28:56 +08:00
<tr><td class="header" colspan="2">Display a the variable "argc" and "argv" every time you stop.</td></tr>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> display argc<br>
<b>(gdb)</b> display argv<br>
</td>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<td class="content">
<b>(lldb)</b> target stop-hook add --one-liner "frame variable argc argv"<br>
<b>(lldb)</b> ta st a -o "fr v argc argv"<br>
<b>(lldb)</b> display argc<br>
<b>(lldb)</b> display argv<br>
</td>
</tr>
<tr><td class="header" colspan="2">Display a the variable "argc" and "argv" only when you stop in the function named <b>main</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
</td>
<td class="content">
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> target stop-hook add --name main --one-liner "frame variable argc argv"<br>
<b>(lldb)</b> ta st a -n main -o "fr v argc argv"<br>
</td>
</tr>
<tr><td class="header" colspan="2">Display the variable "*this" only when you stop in c class named <b>MyClass</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
</td>
<td class="content">
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> target stop-hook add --classname MyClass --one-liner "frame variable *this"<br>
<b>(lldb)</b> ta st a -c MyClass -o "fr v *this"<br>
</td>
</tr>
</table>
<p>
</div>
Add the "expr" command to the gdb command equivalents. llvm-svn: 162617
2012-08-25 06:56:40 +08:00
<h1 class ="postheader">Evaluating expressions</h1>
<div class="post">
<p>
<table class="stats" width="620" cellspacing="0">
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Add the "expr" command to the gdb command equivalents. llvm-svn: 162617
2012-08-25 06:56:40 +08:00
</tr>
<tr><td class="header" colspan="2">Evaluating a generalized expression in the current frame.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> print (int) printf ("Print nine: %d.", 4 + 5)<br>
or if you don't want to see void returns: <br>
<b>(gdb)</b> call (int) printf ("Print nine: %d.", 4 + 5)<br>
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> expr (int) printf ("Print nine: %d.", 4 + 5)<br>
or using the print alias:<br>
<b>(lldb)</b> print (int) printf ("Print nine: %d.", 4 + 5)<br>
</td>
Add the "expr" command to the gdb command equivalents. llvm-svn: 162617
2012-08-25 06:56:40 +08:00
</tr>
<tr><td class="header" colspan="2">Printing the ObjC "description" of an object.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> po [SomeClass returnAnObject]<br>
</td>
Add the "expr" command to the gdb command equivalents. llvm-svn: 162617
2012-08-25 06:56:40 +08:00
<td class="content">
<b>(lldb)</b> expr -o -- [SomeClass returnAnObject]<br>
or using the po alias:<br>
<b>(lldb)</b> po [SomeClass returnAnObject]<br>
</td>
</tr>
<tr><td class="header" colspan="2">Print the dynamic type of the result of an expression.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> set print object 1<br>
<b>(gdb)</b> p someCPPObjectPtrOrReference<br>
only works for C++ objects.<br>
</td>
Add the "expr" command to the gdb command equivalents. llvm-svn: 162617
2012-08-25 06:56:40 +08:00
<td class="content">
<b>(lldb)</b> expr -d 1 -- [SomeClass returnAnObject]<br>
<b>(lldb)</b> expr -d 1 -- someCPPObjectPtrOrReference<br>
or set dynamic type printing to be the default:
<b>(lldb)</b> settings set target.prefer-dynamic run-target<br>
</td>
</tr>
</table>
<p>
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<h1 class ="postheader">Examining Thread State</h1>
<div class="post">
<p>
<table class="stats" width="620" cellspacing="0">
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Show the stack backtrace for the current thread.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> bt<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> thread backtrace<br>
<b>(lldb)</b> bt<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the stack backtraces for all threads.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> thread apply all bt
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> thread backtrace all<br>
<b>(lldb)</b> bt all
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Select a different stack frame by index for the current thread.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> frame 12
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> frame select 12<br>
Improve shortened examples of the watchpoint commands. Document "f <n>" selects frame n. "t <n>" selects thread n but this was just added to TOT so most people won't have access to an lldb that accepts it. llvm-svn: 165332
2012-10-06 04:25:53 +08:00
<b>(lldb)</b> fr s 12<br>
<b>(lldb)</b> f 12<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Add "frame info" command to the "Examining Thread State" section, as suggested by Andrew Trick. llvm-svn: 153204
2012-03-22 02:14:37 +08:00
<tr><td class="header" colspan="2">List information about the currently selected frame in the current thread.</td></tr>
<tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> frame info<br>
Add "frame info" command to the "Examining Thread State" section, as suggested by Andrew Trick. llvm-svn: 153204
2012-03-22 02:14:37 +08:00
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Select the stack frame that called the current stack frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> up
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> up<br>
<b>(lldb)</b> frame select --relative=1<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Select the stack frame that is called by the current stack frame.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> down
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> down<br>
<b>(lldb)</b> frame select --relative=-1<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> fr s -r-1<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Select a different stack frame using a relative offset.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> up 2<br>
<b>(gdb)</b> down 3<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> frame select --relative 2<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> fr s -r2<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<br>
<b>(lldb)</b> frame select --relative -3<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> fr s -r-3<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the general purpose registers for the current thread.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info registers<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> register read<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Added register write examples and also how to modify the pc. For this we show and example of GDB using the "jump" command, and LLDB using "register write" with an expression. llvm-svn: 166127
2012-10-18 04:58:52 +08:00
<tr><td class="header" colspan="2">Write a new decimal value '123' to the current thread register 'rax'.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> p $rax = 123<br>
</td>
<td class="content">
<b>(lldb)</b> register write rax 123<br>
</td>
</tr>
<tr><td class="header" colspan="2">Skip 8 bytes ahead of the current program counter (instruction pointer). Note that we use backticks to evaluate an expression and insert the scalar result in LLDB.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> jump *$pc+8<br>
</td>
<td class="content">
<b>(lldb)</b> register write pc `$pc+8`<br>
</td>
</tr>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<tr><td class="header" colspan="2">Show the general purpose registers for the current thread formatted as <b>signed decimal</b>. LLDB tries to use
the same format characters as <b>printf(3)</b> when possible. Type "help format" to see the full list of format specifiers.</td></tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> register read --format i<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> re r -f i<br>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<br>
<i>LLDB now supports the GDB shorthand format syntax but there can't be space after the command:</i><br>
<b>(lldb)</b> register read/d<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show all registers in all register sets for the current thread.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info all-registers<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> register read --all<br>
<b>(lldb)</b> re r -a<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the values for the registers named "rax", "rsp" and "rbp" in the current thread.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info all-registers rax rsp rbp<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> register read rax rsp rbp<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show the values for the register named "rax" in the current thread formatted as <b>binary</b>.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> p/t $rax<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> register read --format binary rax<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> re r -f b rax<br>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<br>
<i>LLDB now supports the GDB shorthand format syntax but there can't be space after the command:</i><br>
<b>(lldb)</b> register read/t rax<br>
<b>(lldb)</b> p/t $rax<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Read memory from address 0xbffff3c0 and show 4 hex uint32_t values.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> x/4xw 0xbffff3c0<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<td class="content">
<b>(lldb)</b> memory read --size 4 --format x --count 4 0xbffff3c0<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> me r -s4 -fx -c4 0xbffff3c0<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<b>(lldb)</b> x -s4 -fx -c4 0xbffff3c0<br>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<br>
<i>LLDB now supports the GDB shorthand format syntax but there can't be space after the command:</i><br>
<b>(lldb)</b> memory read/4xw 0xbffff3c0<br>
<b>(lldb)</b> x/4xw 0xbffff3c0<br>
<b>(lldb)</b> memory read --gdb-format 4xw 0xbffff3c0<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<tr><td class="header" colspan="2">Read memory starting at the expression "argv[0]".</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> x argv[0]<br>
</td>
Document that we now support the GDB shorthand format syntax on any commands that take formats or sizes. Also document that scalar expression results can be used in any command using expressions inside backticks. llvm-svn: 150652
2012-02-16 10:10:58 +08:00
<td class="content">
<b>(lldb)</b> memory read `argv[0]`<br>
<i><b>NOTE:</b> any command can inline a scalar expression result (as long as the target is stopped) using backticks around any expression:</i><br>
<b>(lldb)</b> memory read --size `sizeof(int)` `argv[0]`<br>
</td>
</tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr><td class="header" colspan="2">Read 512 bytes of memory from address 0xbffff3c0 and save results to a local file as <b>text</b>.</td></tr>
<tr>
<td class="content">
<b>(gdb)</b> set logging on<br>
<b>(gdb)</b> set logging file /tmp/mem.txt<br>
<b>(gdb)</b> x/512bx 0xbffff3c0<br>
<b>(gdb)</b> set logging off<br>
</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(lldb)</b> memory read --outfile /tmp/mem.txt --count 512 0xbffff3c0<br>
<b>(lldb)</b> me r -o/tmp/mem.txt -c512 0xbffff3c0<br>
<b>(lldb)</b> x/512bx -o/tmp/mem.txt 0xbffff3c0<br>
</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">Save binary memory data starting at 0x1000 and ending at 0x2000 to a file.</td></tr>
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> dump memory /tmp/mem.bin 0x1000 0x2000
</td>
<td class="content">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<b>(lldb)</b> memory read --outfile /tmp/mem.bin --binary 0x1000 0x1200<br>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<b>(lldb)</b> me r -o /tmp/mem.bin -b 0x1000 0x1200<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble the current function for the current frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> disassemble
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --frame<br>
<b>(lldb)</b> di -f
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble any functions named <b>main</b>.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> disassemble main
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --name main<br>
<b>(lldb)</b> di -n main
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble an address range.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> disassemble 0x1eb8 0x1ec3
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --start-address 0x1eb8 --end-address 0x1ec3<br>
<b>(lldb)</b> di -s 0x1eb8 -e 0x1ec3<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble 20 instructions from a given address.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> x/20i 0x1eb8
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --start-address 0x1eb8 --count 20<br>
<b>(lldb)</b> di -s 0x1eb8 -c 20<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Show mixed source and disassembly for the current function for the current frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
n/a
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --frame --mixed<br>
<b>(lldb)</b> di -f -m
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble the current function for the current frame and show the opcode bytes.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
n/a
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --frame --bytes<br>
<b>(lldb)</b> di -f -b
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Disassemble the current source line for the current frame.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
n/a
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> disassemble --line<br>
<b>(lldb)</b> di -l
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
</table>
<p>
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div class="postfooter"></div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<h1 class ="postheader">Executable and Shared Library Query Commands</h1>
<div class="post">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<p>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<table class="stats" width="620" cellspacing="0">
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</tr>
<tr><td class="header" colspan="2">List the main executable and all dependent shared libraries.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info shared<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image list<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Remove -w write flag to watch set var from tutorial.html. Fix one gdb example that had an "(lldb)" prompt in the lldb/gdb page. llvm-svn: 166297
2012-10-20 03:52:12 +08:00
<tr><td class="header" colspan="2">Look up information for a raw address in the executable or any shared libraries.</td></tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> info symbol 0x1ec4<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image lookup --address 0x1ec4<br>
<b>(lldb)</b> im loo -a 0x1ec4<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Remove -w write flag to watch set var from tutorial.html. Fix one gdb example that had an "(lldb)" prompt in the lldb/gdb page. llvm-svn: 166297
2012-10-20 03:52:12 +08:00
<tr><td class="header" colspan="2">Look up functions matching a regular expression in a binary.</td></tr>
Add "info func" to the list. llvm-svn: 163669
2012-09-12 08:38:19 +08:00
<tr>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="content">
<b>(gdb)</b> info function &lt;FUNC_REGEX&gt;<br>
</td>
Add "info func" to the list. llvm-svn: 163669
2012-09-12 08:38:19 +08:00
<td class="content">
This one finds debug symbols:<br>
<b>(lldb)</b> image lookup -r -n &lt;FUNC_REGEX&gt;<br><br>
This one finds non-debug symbols:<br>
<b>(lldb)</b> image lookup -r -s &lt;FUNC_REGEX&gt;<br><br>
Provide a list of binaries as arguments to limit the search.
</td>
</tr>
Remove -w write flag to watch set var from tutorial.html. Fix one gdb example that had an "(lldb)" prompt in the lldb/gdb page. llvm-svn: 166297
2012-10-20 03:52:12 +08:00
<tr><td class="header" colspan="2">Look up information for an address in <b>a.out</a> only.</td></tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image lookup --address 0x1ec4 a.out<br>
<b>(lldb)</b> im loo -a 0x1ec4 a.out<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
Remove -w write flag to watch set var from tutorial.html. Fix one gdb example that had an "(lldb)" prompt in the lldb/gdb page. llvm-svn: 166297
2012-10-20 03:52:12 +08:00
<tr><td class="header" colspan="2">Look up information for for a type <code>Point</code> by name.</td></tr>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<tr>
<td class="content">
Remove -w write flag to watch set var from tutorial.html. Fix one gdb example that had an "(lldb)" prompt in the lldb/gdb page. llvm-svn: 166297
2012-10-20 03:52:12 +08:00
<b>(gdb)</b> ptype Point<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image lookup --type Point<br>
<b>(lldb)</b> im loo -t Point<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Dump all sections from the main executable and any shared libraries.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> maintenance info sections<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image dump sections<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Dump all sections in the <b>a.out</b> module.</td></tr>
<tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image dump sections a.out<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Dump all symbols from the main executable and any shared libraries.</td></tr>
<tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image dump symtab<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
<tr><td class="header" colspan="2">Dump all symbols in <b>a.out</b> and <b>liba.so</b>.</td></tr>
<tr>
<td class="content">
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> image dump symtab a.out liba.so<br>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</td>
</tr>
</table>
<p>
</div>
Add "echo" -> "script print". llvm-svn: 156624
2012-05-12 02:01:15 +08:00
<div class="postfooter"></div>
<h1 class ="postheader">Miscellaneous</h1>
<div class="post">
<p>
<table class="stats" width="620" cellspacing="0">
<tr>
<td class="hed" width="50%">GDB</td>
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<td class="hed" width="50%">LLDB</td>
Add "echo" -> "script print". llvm-svn: 156624
2012-05-12 02:01:15 +08:00
</tr>
<tr><td class="header" colspan="2">Echo text to the screen.</td></tr>
<tr>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(gdb)</b> echo Here is some text\n<br>
Add "echo" -> "script print". llvm-svn: 156624
2012-05-12 02:01:15 +08:00
</td>
<td class="content">
Swap the columns in the lldb & gdb command comparison table. I often hear feedback from people that having the lldb commands on the left hand side is non-intuitive -- they say "I want a *gdb* to *lldb* table, not a *lldb* to *gdb* table". It doesn't seem odious to go from the right-hand column to the left hand column but I've heard this same feedback enough that it's also pointless to keep the format lldb-first, gdb-second when it was an arbitrary choice to begin with. llvm-svn: 165294
2012-10-05 12:26:06 +08:00
<b>(lldb)</b> script print &quot;Here is some text&quot;<br>
Add "echo" -> "script print". llvm-svn: 156624
2012-05-12 02:01:15 +08:00
</td>
</tr>
</table>
<p>
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
<div class="postfooter"></div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
<p>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</div>
Add examples of shortest-possible lldb commands where appropriate. Add new "Examining Variables" section. Updated a few command entries to match current lldb behavior. llvm-svn: 142898
2011-10-25 09:28:31 +08:00
</div>
</div>
Document nexti, show some shorter versions of long lldb commands. llvm-svn: 142715
2011-10-22 10:31:42 +08:00
</div>
</body>
</html>