10 More Discussions You Might Find Interesting
1. Hardware
What are the steps you need to take when you put an old HD in a new computer? I just did this. Every time it makes it to the windows boot screen then restarts. I have a bunch of old engineering software that is not compatible with the newer versions of windows. I figured this out after I bought... (6 Replies)
Discussion started by: cokedude
6 Replies
2. Shell Programming and Scripting
I already manage to get the output that i want.. but wat if removing all the pipes and convert it 1 liner with less pipes. My command below can get the ouput that i want. i just want to remove the pipes or less pipes.
#cat file1
us-west-2a running i-3397a421... (2 Replies)
Discussion started by: kenshinhimura
2 Replies
3. UNIX for Dummies Questions & Answers
Hello ,
I am searching a directory for a file and have to assign the filename to a variable .
The variable must have form $$filename
So my code is
echo "'$$filename='`ls -lrt *PreMatch*.csv| head -1 | nawk '{print $9}'`"
however $$ is converting to a number .
How could I make it $$... (3 Replies)
Discussion started by: Pratik4891
3 Replies
4. Shell Programming and Scripting
Hi,
I generated many figures in .png format (approximately 120). Right now I need to pair the figures on a single page so that the files with the same file name (i.e. jack) that end with .matrix.png are placed on the left and .cdt.png is on the right (so jack.matrix.png with jack.cdt.png... (6 Replies)
Discussion started by: kylle345
6 Replies
5. UNIX for Advanced & Expert Users
When we put a breakpoint using gcc then what all things happen internally and how the gdb using break is able to pause the execution of process( instead of killing it ) and later on resume the process execution? (0 Replies)
Discussion started by: rupeshkp728
0 Replies
6. UNIX for Advanced & Expert Users
I have Suse linux-2.6.31.5-0.1.
When I try to set breakpoint in application or kernel modules it gives me command not found error.
For instance
when I typed the command
b xyz.c:47
it gives me an error:
"If 'b' is not a typo you can use command-not-found lookup the package that contains... (4 Replies)
Discussion started by: rupeshkp728
4 Replies
7. UNIX for Advanced & Expert Users
Dear all:
(gdb) add-symbol-file /home/likunlun/rtl8139_driver.ko 0xf80e5000 -s .bss 0xf80e72d4 -s .data 0xf80e70e0
add symbol table from file "/home/likunlun/rtl8139_driver.ko" at
.text_addr = 0xf80e5000
.bss_addr = 0xf80e72d4
.data_addr = 0xf80e70e0
(y or n) y
Reading symbols... (6 Replies)
Discussion started by: liklstar
6 Replies
8. Shell Programming and Scripting
I want a way to put a break point in gdb by runing a shell script.
Actualy I wanted to do certain automisation of a long manual process, which includes starting of a process in background and then taking the process ID of that process and then attach the gdb to that process ID. Then finaly... (4 Replies)
Discussion started by: kapilkumawat
4 Replies
9. UNIX for Dummies Questions & Answers
Can anybody tell What is the exact difference between a Dual-core processor and a Core-to-duo processor ?Advance thanks to all my friends. (1 Reply)
Discussion started by: Ajith kumar.G
1 Replies
10. UNIX for Dummies Questions & Answers
How do I put a my PC with linux 7.0 on a class B network.
Can someone give me info or text that will guide me? (1 Reply)
Discussion started by: Rush
1 Replies
LLDB(1) BSD General Commands Manual LLDB(1)
NAME
lldb -- The debugger
SYNOPSIS
lldb [-hvdexw] [-a arch] [-l script-language] [-s lldb-commands] [-n process-name] [-p pid] [[--] <PROGRAM-ARG1> <PROGRAM-ARG2> ...]
DESCRIPTION
lldb is the command line interface for the LLDB debugger library. lldb can debug C, C++, Objective-C, and Objective-C++ programs.
The following options are available:
-h, --help
Prints out the usage information for the lldb debugger. The --help text may be more up-to-date and authoritative than the command
line options described in this man page.
-v, --version
Prints out the version number of the lldb debugger.
-a, --arch arch
Specifies which architecture lldb will use when launching the specified program (assuming the provided executable is built for multi-
ple architectures.)
-f, --file filename
Specifies the executable file that will be launching / attaching to.
-n, --attach-name process-name
Specifies the name of a currently-running process to attach to. (or the name of a process to wait for if -w is used.)
-w, --wait-for
When used in concert with -n process-name-E, indicates that lldb should wait for a new process of that name to be started -- and
attach to it as early in the process-launch as possible.
-p, --attach-pid pid
Specifies a currently running process that lldb should attach to.
-l, --script-language language
Tells the debugger to use the specified scripting language for user-defined scripts, rather than the default. Valid scripting lan-
guages that can be specified include Python, Perl, Ruby and Tcl. Currently only the Python extensions have been implemented.
-d, --debug
Tells the debugger to print out extra information for debugging itself.
-s, --source filename
Tells lldb to read in and execute the file "filename", which should contain lldb commands.
-e, --editor
Instructs lldb to open source files using the host's "external editor" mechanism.
-x, --no-lldbinit
Do not automatically parse any '.lldbinit' files.
(If you don't provide -f then the first argument will be the file to be debugged so 'lldb -- <filename> [<ARG1> [<ARG2>]]' also
works. Remember to end the options with "--" if any of your arguments have a "-" in them.)
USING LLDB
In lldb there is a help command which can be used to find descriptions and examples of all lldb commands. To get help on "breakpoint set"
you would type "help breakpoint set".
There is also an apropos command which will search the help text of all commands for a given term -- this is useful for locating a command by
topic. For instance, "apropos breakpoint" will list any command that has the word breakpoint in its help text.
FILES
lldb will read settings/aliases/commands from three files at startup, if they exist.
First, it will read a ~/.lldbinit-debugger command file. If you are using the lldb command line interface, this is ~/.lldbinit-lldb. If you
are using lldb inside a GUI debugger like Xcode this will be ~/.lldbinit-Xcode. This is a useful place to put settings that you want to
apply only when a given lldb command interpreter is used.
Second, ~/.lldbinit is read.
Third, an .lldbinit file in the current working directory (where lldb is started) will be read.
SEE ALSO
The LLDB project page http://lldb.llvm.org/ has many different resources for lldb users -- the gdb/lldb command equivalence page
http://lldb.llvm.org/lldb-gdb.html can be especially helpful for users coming from gdb.
BUGS
To report bugs, please visit http://llvm.org/bugs/
AUTHOR
Maintained by the LLDB Team, http://lldb.llvm.org/
Darwin 7 June, 2012 Darwin