01-20-2011
Perderabo:
Amaizing!
What the commands are the 'l' and 'S'?
The 'S' I guess, kind of 'search'?
OK, I have found: that is the debugger commands!
Anyway, BIG THANK YOU!
That exactly what I was looking for!
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Can you please let me know if there's any debug command for perl scripts
like
set -x for shell scripts (2 Replies)
Discussion started by: dayanandra
2 Replies
2. Shell Programming and Scripting
I installed Net::sftp on a solaris 8 server and I am able to successfully transfer files to the remote server. I am running the command out of a script with debug=1 on so I can see the verbose output.
The last two lines of the debug output show it couldn't fsetstat, but I don't know what that... (2 Replies)
Discussion started by: csgonan
2 Replies
3. Shell Programming and Scripting
Hi All,
Does perl has an interactive mode like other shell?
If there is, can any one show me the equivalent code for the below csh script ? This csh code prompts user for their name and prints the name.
#!/bin/csh
echo -n "Pls enter the your name: "
set name = ($<)
echo "You hav... (2 Replies)
Discussion started by: Raynon
2 Replies
4. Shell Programming and Scripting
HI All,
NET::FTP->new($server, DEBUG=>1);
I need to get all the Debug Messages in an array or a file....
Please suggest!! (0 Replies)
Discussion started by: angad.makkar
0 Replies
5. Shell Programming and Scripting
When I run a lengthy script in debug mode i need to capture all the steps which are executed.
e.g
ksh -x script.ksh
+ test -f /proc/mounts
+ /bin/ls -l /proc/21326/exe
+ is=ksh
+ test ksh = ksh
+ test -s /etc/ksh.kshrc
+ . /etc/ksh.kshrc
+ trap 1 2 3
+ who am i
+ awk {print $1}
+... (2 Replies)
Discussion started by: zooby
2 Replies
6. Programming
Hi,
plz see the below code , i have catch the file "Orders.20110714.out "file
as a Orders*.out. but it giving me an error .it does not open the file.
if the same thing i have done by code
code-> ls Orders*.out then it gives me the output
Orders.20110714.out
i am trying apply the... (1 Reply)
Discussion started by: pspriyanka
1 Replies
7. Shell Programming and Scripting
I have a shell program which calls a perl program.
I am running the shell program with command;
$ ksh -x <prog_name>
Inside the shell program, I am calling perl with warnings.
I want to capture the entire output as it comes on screen.
The command I tried is:
$ ksh -x... (1 Reply)
Discussion started by: som.nitk
1 Replies
8. Shell Programming and Scripting
Hi,
I am trying to get squid up and running using a redirector process, and every time I try to load a web page, squid fails miserably.
Can some one with perl and squid knowledge take a look at these codes and tell if something is wrong here.
#!/usr/bin/perl
#
$| = 1;
@endings = qw/... (0 Replies)
Discussion started by: jamie_123
0 Replies
9. Shell Programming and Scripting
I am new to perl and want to get a little better understanding of debugging code in perl. I have a perl script that has questions to be answered like:
he following PERL modules are recommended:
Crypt::DES
Crypt::PasswdMD5
IO::Pty
Net::Write::Layer2
String::CRC32
Attempt to install... (0 Replies)
Discussion started by: metallica1973
0 Replies
10. Programming
I have reviewed many examples on-line about running another process (either PERL or shell command or a program), but do not find any usefull for my needs way. (Reviewed and not useful the system(), 'back ticks', exec() and open())
I would like to run another PERL-script from first one, not... (1 Reply)
Discussion started by: alex_5161
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