Hi;
Thanks for replying, sorry for my delayed response.
Code:
cat test.sh
#!/bin/bash
expect -c "
set multilinetext 'first one two
second one two three
third one
fourth one two three four
fifth one two'
;"
Error:
./test.sh
wrong # args: should be "set varName ?newValue?"
while executing
"set multilinetext 'first one two"
It looks that the "-c" commands calling parameter in bash, can create number of different errors.
I am now trying to separate all Expect from Bash - Expect dedicated files called from main bash files.
It seems to have lots of benefits, also some drawbacks.
Moderator's Comments:
Please wrap all code, files, input & output/errors in CODE tags for clarity.
It also preserves spaces for indenting or fixed-width data.
Howdie everyone...
I have a shell script RemoveFiles.sh
Inside this file, it only has two commands as below:
rm -f ../../reportToday/temp/*
rm -f ../../report/*
My problem is that when i execute this script, nothing happened. Files remained unremoved. I don't see any error message as it... (2 Replies)
Hello all,
The following script (sess.sh) runs fine and gives the correct output on a SunOS 5.9 ( default shell =/bin/ksh) but gives incorrect results on a SunOS 5.7 (default shell= /bin/sh). The script logs on to an oracle database and queries the total no of sessions running in the database... (6 Replies)
Hello to all...this is my first post (so please go easy). :)
I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Hi All,
Using Expect script when I run it manually it works. But when I put the entry in crontab, the job is still running after 15 hours. The script was created as root. I don't think it's a permission issue. Any idea?
This is what I have under root crontab...
00 18 * * 1-5... (4 Replies)
I have a really basic expect script which I call from php. I works fine when I run the php from the shell, but from the web it appears as if the output buffer gets chopped and never gets all of the contents.
php script: (runexpect.php)
<?php... (7 Replies)
Hi all,
I'm new in this forum.
I'm looking for the difference between the HACMP commands with the prefix "cl" and "cli".
The first type are under /usr/es/sbin/cluster/sbin directory and the second are under /usr/es/sbin/cluster/cspoc directory.
I know that the first are called HACMP for AIX... (0 Replies)
Guys,
I need you help please.
The script below is not working correclty for checking via a awk/if statement . Can you tell me what i am doing wrong in the script code "if($1 == "$RETENTION_LEVEL") "
Syntax
RETENTION_LEVEL=`echo $LINE | cut -f2 -d" "`
echo " ==============... (4 Replies)
Greetings, I have a C-program that is made to implement a hidden Markov model on an input file. The program is very memory intensive.
I've installed it on my local server where I have an account and it compiles fine. The way they have the server set up is that you can either work... (1 Reply)
I'm having a problem scripting Expect to work as a Nagios check. The script runs fine from the cli, but not when run as a Nagios check. I turn on the debug output, and it looks like it's not seeing the whole buffer's worth of info, like it's paged interactively somehow. I'm new to Expect, but this... (1 Reply)
The below command works in the terminal interactively but not as part of a bash script. I though maybe I needed to escape the "$dir" so it isn't interpreted literally, but that's not it. Thank you :).
interactively in terminal
dir=/path/to
new=$(ls "$dir"/*.csv -tr | tail -n 1) && echo... (6 Replies)
Discussion started by: cmccabe
6 Replies
LEARN ABOUT FREEBSD
lldb
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
09-02-2019
