@dcci
The Command invoked has following parameter:
--executable /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb
I tried the following basic verification:-
sar@267538d18c75:~$ ll /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb -rwxr-xr-x 1 sar sar 409432 Mar 1 07:04 /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb*
sar@267538d18c75:~$ /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb --help
OVERVIEW: LLDB
USAGE: lldboptions
ATTACHING:
--attach-name <name> Tells the debugger to attach to a process with the given name.
--attach-pid <pid> Tells the debugger to attach to a process with the given pid.
-n <value> Alias for --attach-name
-p <value> Alias for --attach-pid
--wait-for Tells the debugger to wait for a process with the given pid or name to launch before attaching.
-w Alias for --wait-for
COMMANDS:
--batch Tells the debugger to run the commands from -s, -S, -o & -O, and then quit.
-b Alias for --batch
-K <value> Alias for --source-on-crash
-k <value> Alias for --one-line-on-crash
--no-lldbinit Do not automatically parse any '.lldbinit' files.
--one-line-before-file <command>
Tells the debugger to execute this one-line lldb command before any file provided on the command line has been loaded.
--one-line-on-crash <command>
When in batch mode, tells the debugger to source this file of lldb commands if the target crashes.
--one-line <command> Tells the debugger to execute this one-line lldb command after any file provided on the command line has been loaded.
-O <value> Alias for --one-line-before-file
-o <value> Alias for --one-line
-Q Alias for --source-quietly
--source-before-file <file>
Tells the debugger to read in and execute the lldb commands in the given file, before any file has been loaded.
--source-on-crash <file>
When in batch mode, tells the debugger to source this file of lldb commands if the target crashes.
--source-quietly Tells the debugger to execute this one-line lldb command before any file has been loaded.
--source <file> Tells the debugger to read in and execute the lldb commands in the given file, after any file has been loaded.
-S <value> Alias for --source-before-file
-s <value> Alias for --source
-x Alias for --no-lldbinit
OPTIONS:
--arch <architecture> Tells the debugger to use the specified architecture when starting and running the program.
-a <value> Alias for --arch
--capture <filename> Tells the debugger to capture a reproducer to <filename>.
--core <filename> Tells the debugger to use the full path to <filename> as the core file.
-c <value> Alias for --core
--debug Tells the debugger to print out extra information for debugging itself.
-d Alias for --debug
--editor Tells the debugger to open source files using the host's "external editor" mechanism.
-e Alias for --editor
--file <filename> Tells the debugger to use the file <filename> as the program to be debugged.
-f <value> Alias for --file
--help Prints out the usage information for the LLDB debugger.
-h Alias for --help
--no-use-colors Do not use colors.
--replay <filename> Tells the debugger to replay a reproducer from <filename>.
--version Prints out the current version number of the LLDB debugger.
-v Alias for --version
-X Alias for --no-use-color
REPL:
-r=<flags> Alias for --repl=<flags>
--repl-language <language>
Chooses the language for the REPL.
--repl=<flags> Runs lldb in REPL mode with a stub process with the given flags.
--repl Runs lldb in REPL mode with a stub process.
-R <value> Alias for --repl-language
-r Alias for --repl
SCRIPTING:
-l <value> Alias for --script-language
--python-path Prints out the path to the lldb.py file for this version of lldb.
-P Alias for --python-path
--script-language <language>
Tells the debugger to use the specified scripting language for user-defined scripts.
EXAMPLES:
The debugger can be started in several modes.
Passing an executable as a positional argument prepares lldb to debug the
given executable. Arguments passed after -- are considered arguments to the
debugged executable.
lldb --arch x86_64 /path/to/program -- --arch arvm7
Passing one of the attach options causes lldb to immediately attach to the
given process.
lldb -p <pid>
lldb -n <process-name>
Passing --repl starts lldb in REPL mode.
lldb -r
Passing --core causes lldb to debug the core file.
lldb -c /path/to/core
Command options can be combined with either mode and cause lldb to run the
specified commands before or after events, like loading the file or crashing,
in the order provided on the command line.
lldb -O 'settings set stop-disassembly-count 20' -o 'run' -o 'bt'
lldb -S /source/before/file -s /source/after/file
lldb -K /source/before/crash -k /source/after/crash
sar@267538d18c75:~$ /home/sar/swift-source/build/buildbot_linux/lldb-linux-powerpc64le/./bin/lldb
(lldb) script print "Here is some text"
Here is some text
(lldb) help
Debugger commands:
apropos -- List debugger commands related to a word or subject.
breakpoint -- Commands for operating on breakpoints (see 'help b' for shorthand.)
bugreport -- Commands for creating domain-specific bug reports.
command -- Commands for managing custom LLDB commands.
disassemble -- Disassemble specified instructions in the current target. Defaults to the current function for the current thread and
stack frame.
expression -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
frame -- Commands for selecting and examing the current thread's stack frames.
gdb-remote -- Connect to a process via remote GDB server. If no host is specifed, localhost is assumed.
gui -- Switch into the curses based GUI mode.
help -- Show a list of all debugger commands, or give details about a specific command.
kdp-remote -- Connect to a process via remote KDP server. If no UDP port is specified, port 41139 is assumed.
language -- Commands specific to a source language.
log -- Commands controlling LLDB internal logging.
memory -- Commands for operating on memory in the current target process.
platform -- Commands to manage and create platforms.
plugin -- Commands for managing LLDB plugins.
process -- Commands for interacting with processes on the current platform.
quit -- Quit the LLDB debugger.
register -- Commands to access registers for the current thread and stack frame.
reproducer -- Commands controlling LLDB reproducers.
script -- Invoke the script interpreter with provided code and display any results. Start the interactive interpreter if no
code is supplied.
settings -- Commands for managing LLDB settings.
source -- Commands for examining source code described by debug information for the current target process.
statistics -- Print statistics about a debugging session
target -- Commands for operating on debugger targets.
thread -- Commands for operating on one or more threads in the current process.
type -- Commands for operating on the type system.
version -- Show the LLDB debugger version.
watchpoint -- Commands for operating on watchpoints.
Current command abbreviations (type 'help command alias' for more info):
add-dsym -- Add a debug symbol file to one of the target's current modules by specifying a path to a debug symbols file, or using the
options to specify a module to download symbols for.
attach -- Attach to process by ID or name.
b -- Set a breakpoint using one of several shorthand formats.
bt -- Show the current thread's call stack. Any numeric argument displays at most that many frames. The argument 'all' displays
all threads.
c -- Continue execution of all threads in the current process.
call -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
continue -- Continue execution of all threads in the current process.
detach -- Detach from the current target process.
di -- Disassemble specified instructions in the current target. Defaults to the current function for the current thread and stack
frame.
dis -- Disassemble specified instructions in the current target. Defaults to the current function for the current thread and stack
frame.
display -- Evaluate an expression at every stop (see 'help target stop-hook'.)
down -- Select a newer stack frame. Defaults to moving one frame, a numeric argument can specify an arbitrary number.
env -- Shorthand for viewing and setting environment variables.
exit -- Quit the LLDB debugger.
f -- Select the current stack frame by index from within the current thread (see 'thread backtrace'.)
file -- Create a target using the argument as the main executable.
finish -- Finish executing the current stack frame and stop after returning. Defaults to current thread unless specified.
image -- Commands for accessing information for one or more target modules.
j -- Set the program counter to a new address.
jump -- Set the program counter to a new address.
kill -- Terminate the current target process.
l -- List relevant source code using one of several shorthand formats.
list -- List relevant source code using one of several shorthand formats.
n -- Source level single step, stepping over calls. Defaults to current thread unless specified.
next -- Source level single step, stepping over calls. Defaults to current thread unless specified.
nexti -- Instruction level single step, stepping over calls. Defaults to current thread unless specified.
ni -- Instruction level single step, stepping over calls. Defaults to current thread unless specified.
p -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
parray -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
po -- Evaluate an expression on the current thread. Displays any returned value with formatting controlled by the type's author.
poarray -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
print -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
q -- Quit the LLDB debugger.
r -- Launch the executable in the debugger.
rbreak -- Sets a breakpoint or set of breakpoints in the executable.
repl -- Evaluate an expression on the current thread. Displays any returned value with LLDB's default formatting.
run -- Launch the executable in the debugger.
s -- Source level single step, stepping into calls. Defaults to current thread unless specified.
si -- Instruction level single step, stepping into calls. Defaults to current thread unless specified.
sif -- Step through the current block, stopping if you step directly into a function whose name matches the TargetFunctionName.
step -- Source level single step, stepping into calls. Defaults to current thread unless specified.
stepi -- Instruction level single step, stepping into calls. Defaults to current thread unless specified.
t -- Change the currently selected thread.
tbreak -- Set a one-shot breakpoint using one of several shorthand formats.
undisplay -- Stop displaying expression at every stop (specified by stop-hook index.)
up -- Select an older stack frame. Defaults to moving one frame, a numeric argument can specify an arbitrary number.
v -- Show variables for the current stack frame. Defaults to all arguments and local variables in scope. Names of argument, local,
file static and file global variables can be specified. Children of aggregate variables can be specified such as
'var->child.x'. The -> and [] operators in 'frame variable' do not invoke operator overloads if they exist, but directly
access the specified element. If you want to trigger operator overloads use the expression command to print the variable
instead.
It is worth noting that except for overloaded operators, when printing local variables 'expr local_var' and 'frame var
local_var' produce the same results. However, 'frame variable' is more efficient, since it uses debug information and memory
reads directly, rather than parsing and evaluating an expression, which may even involve JITing and running code in the target
program.
var -- Show variables for the current stack frame. Defaults to all arguments and local variables in scope. Names of argument, local,
file static and file global variables can be specified. Children of aggregate variables can be specified such as
'var->child.x'. The -> and [] operators in 'frame variable' do not invoke operator overloads if they exist, but directly
access the specified element. If you want to trigger operator overloads use the expression command to print the variable
instead.
It is worth noting that except for overloaded operators, when printing local variables 'expr local_var' and 'frame var
local_var' produce the same results. However, 'frame variable' is more efficient, since it uses debug information and memory
reads directly, rather than parsing and evaluating an expression, which may even involve JITing and running code in the target
program.
vo -- Show variables for the current stack frame. Defaults to all arguments and local variables in scope. Names of argument, local,
file static and file global variables can be specified. Children of aggregate variables can be specified such as
'var->child.x'. The -> and [] operators in 'frame variable' do not invoke operator overloads if they exist, but directly
access the specified element. If you want to trigger operator overloads use the expression command to print the variable
instead.
It is worth noting that except for overloaded operators, when printing local variables 'expr local_var' and 'frame var
local_var' produce the same results. However, 'frame variable' is more efficient, since it uses debug information and memory
reads directly, rather than parsing and evaluating an expression, which may even involve JITing and running code in the target
program.
x -- Read from the memory of the current target process.
For more information on any command, type 'help <command-name>'.
(lldb)
Anything else that I should be trying/verifying?
