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