1 .Dd December 16, 2015 \" DATE
2 .Dt LLDB 1 \" Program name and manual section number
4 .Sh NAME \" Section Header - required - do not modify
7 .Sh SYNOPSIS \" Section Header - required - do not 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 - do not 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
31 text may be more up-to-date and
32 authoritative than the command line options described in this man
35 Prints out the version number of the
38 .It Fl a, -arch Ar arch
39 Specifies which architecture
41 will use when launching the specified program (assuming the provided
42 executable is built for multiple architectures.)
43 .It Fl f, -file Ar filename
44 Specifies the executable file that
46 will be launching / attaching to.
47 .It Fl n, -attach-name Ar process-name
48 Specifies the name of a currently-running process to attach to.
49 (or the name of a process to wait for if
53 When used in concert with
54 .Fl n Ar process-name ,
57 should wait for a new process of that name to be started -- and attach
58 to it as early in the process-launch as possible.
59 .It Fl p, -attach-pid Ar pid
60 Specifies a currently running process that
63 .It Fl c, -core Ar core-file
64 Specifies the core file to examine.
65 .It Fl l, -script-language Ar language
66 Tells the debugger to use the specified scripting language for
67 user-defined scripts, rather than the default.
69 languages that can be specified include Python, Perl, Ruby and Tcl.
70 Currently only the Python extensions have been implemented.
72 Tells the debugger to print out extra information for debugging itself.
73 .It Fl s, -source Ar filename
76 to read in and execute the file
84 to open source files using the host's "external editor" mechanism.
85 .It Fl x, -no-lldbinit
86 Do not automatically parse any '.lldbinit' files.
88 (If you do not provide -f then the first argument will be the file to
90 so 'lldb -- <filename> [<ARG1> [<ARG2>]]' also works.
91 Remember to end the options with "--" if any of your arguments have
99 command which can be used to find descriptions and examples of all
103 .Qq Cm breakpoint set
105 .Qq Cm help breakpoint set .
109 command which will search the help text of all commands
110 for a given term -- this is useful for locating a command by topic.
112 .Qq Cm apropos breakpoint
113 will list any command that has the word
118 will read settings/aliases/commands from three files at startup, if they exist.
120 First, it will read a
121 .Pa ~/.lldbinit-debugger
125 command line interface, this is
126 .Pa ~/.lldbinit-lldb .
129 inside a GUI debugger like
132 .Pa ~/.lldbinit-Xcode .
133 This is a useful place to put settings that you want to apply only when a given
135 command interpreter is used.
143 file in the current working directory (where
145 is started) will be read.
147 The LLDB project page http://lldb.llvm.org/ has many different resources for
149 users -- the gdb/lldb command equivalence page http://lldb.llvm.org/lldb-gdb.html can
150 be especially helpful for users coming from gdb.
152 To report bugs, please visit http://llvm.org/bugs/
154 Maintained by the LLDB Team, http://lldb.llvm.org/