1 .Dd 7 June, 2012 \" DATE
2 .Dt LLDB 1 \" Program name and manual section number
3 .Os Darwin \" Operating System
4 .Sh NAME \" Section Header - required - don't modify
7 .Sh SYNOPSIS \" Section Header - required - don't modify
11 .Op Fl l Ar script-language
12 .Op Fl s Ar lldb-commands
13 .Op Fl n Ar process-name
15 .Ar [[--] <PROGRAM-ARG1> <PROGRAM-ARG2> ...]
16 .Sh DESCRIPTION \" Section Header - required - don't modify
18 is the command line interface for the LLDB debugger library.
20 can debug C, C++, Objective-C, and Objective-C++ programs.
22 The following options are available:
23 .Bl -tag -width indent
25 Prints out the usage information for the
27 debugger. The \fB\-\-help\fR text may be more up-to-date and
28 authoritative than the command line options described in this man
31 Prints out the version number of the
34 .It Fl a, -arch Ar arch
35 Specifies which architecture
37 will use when launching the specified program (assuming the provided
38 executable is built for multiple architectures.)
39 .It Fl f, -file Ar filename
40 Specifies the executable file that
42 will be launching / attaching to.
43 .It Fl n, -attach-name Ar process-name
44 Specifies the name of a currently-running process to attach to.
45 (or the name of a process to wait for if \fB\-w\fR is used.)
47 When used in concert with \&\fB\-n process-name\-E\fR, indicates that
49 should wait for a new process of that name to be started -- and attach
50 to it as early in the process-launch as possible.
51 .It Fl p, -attach-pid Ar pid
52 Specifies a currently running process that
55 .It Fl l, -script-language Ar language
56 Tells the debugger to use the specified scripting language for
57 user-defined scripts, rather than the default. Valid scripting
58 languages that can be specified include Python, Perl, Ruby and Tcl.
59 Currently only the Python extensions have been implemented.
61 Tells the debugger to print out extra information for debugging itself.
62 .It Fl s, -source Ar filename
65 to read in and execute the file "\fBfilename\fR", which
72 to open source files using the host's "external editor" mechanism.
73 .It Fl x, -no-lldbinit
74 Do not automatically parse any '.lldbinit' files.
76 (If you don't provide -f then the first argument will be the file to be debugged
77 so 'lldb -- <filename> [<ARG1> [<ARG2>]]' also works.
78 Remember to end the options with "--" if any of your arguments have a "-" in them.)
83 there is a \fBhelp\fR command which can be used to find descriptions and examples of
86 commands. To get help on "\fBbreakpoint set\fR" you would type "\fBhelp breakpoint set\fR".
88 There is also an \fBapropos\fR command which will search the help text of all commands
89 for a given term -- this is useful for locating a command by topic. For instance, "\fBapropos breakpoint\fR"
90 will list any command that has the word \fBbreakpoint\fR in its help text.
93 will read settings/aliases/commands from three files at startup, if they exist.
95 First, it will read a \fB~/.lldbinit-\fIdebugger\fR command file. If you are using the
97 command line interface, this is \fB~/.lldbinit-lldb\fR. If you are using
99 inside a GUI debugger like
101 this will be \fB~/.lldbinit-Xcode\fR. This is a useful place to put settings that you
102 want to apply only when a given
104 command interpreter is used.
106 Second, \fB~/.lldbinit\fR is read.
108 Third, an \fR.lldbinit\fR file in the current working directory (where
110 is started) will be read.
112 The LLDB project page http://lldb.llvm.org/ has many different resources for
114 users -- the gdb/lldb command equivalence page http://lldb.llvm.org/lldb-gdb.html can
115 be especially helpful for users coming from gdb.
117 To report bugs, please visit http://llvm.org/bugs/
119 Maintained by the LLDB Team, http://lldb.llvm.org/