10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am not able to run below command on linux, it however works on solaris. If anyone knows the reason and a solution for it can you please let me know ?
Linux
-----
$> ksh 'echo hi'
ksh: echo hi: No such file or directory
$> which ksh
/usr/bin/ksh
Solaris
------
$> ksh 'echo... (2 Replies)
Discussion started by: krishnaux
2 Replies
2. Shell Programming and Scripting
i have four commands
1. perl -MCPAN -e shell
2. o conf prerequisites_policy follow
3. o conf commit
4. exit
I am attempting to streamline a bunch of yum commands and cpan installations and want to remove the confirmation portion of the cpan these four commands will do just that. my... (2 Replies)
Discussion started by: murphybr
2 Replies
3. UNIX for Advanced & Expert Users
I have an Oracle database running on AIX, and I have a procedure that is calling OS commands from an oracle (and it's not working anymore)...
so, there was an Java stored proc in Oracle
CREATE OR REPLACE AND RESOLVE JAVA SOURCE NAMED COMMON."Host" as import java.io.*;
public class Host {... (1 Reply)
Discussion started by: bongo
1 Replies
4. Shell Programming and Scripting
Hello gurus,
I have three korn shell script 3.1, 3.2, 3.3. I would like to call three shell script in one shell script.
i m looking for something like this
call 3.1;
If 3.1 = "complete" then
call 3.2;
if 3.2 = ''COMPlete" then
call 3.3;
else
exit
The... (1 Reply)
Discussion started by: shashi369
1 Replies
5. 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
6. Programming
hi Guys,
I am planning to write a program which can be able to execute scripts/commands which needs a user to be root.
Note: we are not interested to use sudoers option.
.e.g. The requirement can be explaind as:
A normal UNIX system user cannot execute above command(veritas cluster... (3 Replies)
Discussion started by: Asteroid
3 Replies
7. Shell Programming and Scripting
I want to log into a remote server transfer over a new config and then backup the existing config, replace with the new config.
I am not sure if I can do this with BASH scripting.
I have set up password less login by adding my public key to authorized_keys file, it works.
I am a little... (1 Reply)
Discussion started by: bash_in_my_head
1 Replies
8. Shell Programming and Scripting
Hi,
I have a query ..
i have 2 scripts say 1.sh and 2.sh
1.sh contains many functions written using shell scripts.
2.sh is a script which needs to call the functions definded in 1.sh
function calls are with arguments.
Can some one tell me how to call the functions from 2.sh?
Thanks in... (6 Replies)
Discussion started by: jisha
6 Replies
9. Shell Programming and Scripting
if ( system ("/bin/cat $File1 >> $File2") ) {
print("#WARNING RAISED : /bin/cat File1 >> File2 - FAILURE!\n"); } I came across this code, would appreciate if someone can tell me if my understanding is correct?
the perl code tell the system to cat file 1 into file 2, if command fails, print... (4 Replies)
Discussion started by: new2ss
4 Replies
10. Shell Programming and Scripting
hi friends,
i'm new to unix and straight away i had to start with the script files.
I've a script file which gets called from a menu item on a GUI.
This script file again calls .awk file, in performing some tasks , which also generates certain files.
I modified the files to generate some... (1 Reply)
Discussion started by: Ravi_Kandula
1 Replies
VGDB(1) Release 3.9.0 VGDB(1)
NAME
vgdb - intermediary between Valgrind and GDB or a shell
SYNOPSIS
vgdb [options]
DESCRIPTION
vgdb ("Valgrind to GDB") is used as an intermediary between Valgrind and GDB or a shell. It has two usage modes:
1. As a standalone utility, it is used from a shell command line to send monitor commands to a process running under Valgrind. For this
usage, the vgdb OPTION(s) must be followed by the monitor command to send. To send more than one command, separate them with the -c
option.
2. In combination with GDB "target remote |" command, it is used as the relay application between GDB and the Valgrind gdbserver. For this
usage, only OPTION(s) can be given, but no COMMAND can be given.
OPTIONS
--pid=<number>
Specifies the PID of the process to which vgdb must connect to. This option is useful in case more than one Valgrind gdbserver can be
connected to. If the --pid argument is not given and multiple Valgrind gdbserver processes are running, vgdb will report the list of
such processes and then exit.
--vgdb-prefix
Must be given to both Valgrind and vgdb if you want to change the default prefix for the FIFOs (named pipes) used for communication
between the Valgrind gdbserver and vgdb.
--wait=<number>
Instructs vgdb to search for available Valgrind gdbservers for the specified number of seconds. This makes it possible start a vgdb
process before starting the Valgrind gdbserver with which you intend the vgdb to communicate. This option is useful when used in
conjunction with a --vgdb-prefix that is unique to the process you want to wait for. Also, if you use the --wait argument in the GDB
"target remote" command, you must set the GDB remotetimeout to a value bigger than the --wait argument value. See option
--max-invoke-ms (just below) for an example of setting the remotetimeout value.
--max-invoke-ms=<number>
Gives the number of milliseconds after which vgdb will force the invocation of gdbserver embedded in Valgrind. The default value is 100
milliseconds. A value of 0 disables forced invocation. The forced invocation is used when vgdb is connected to a Valgrind gdbserver,
and the Valgrind process has all its threads blocked in a system call.
If you specify a large value, you might need to increase the GDB "remotetimeout" value from its default value of 2 seconds. You should
ensure that the timeout (in seconds) is bigger than the --max-invoke-ms value. For example, for --max-invoke-ms=5000, the following GDB
command is suitable:
(gdb) set remotetimeout 6
--cmd-time-out=<number>
Instructs a standalone vgdb to exit if the Valgrind gdbserver it is connected to does not process a command in the specified number of
seconds. The default value is to never time out.
--port=<portnr>
Instructs vgdb to use tcp/ip and listen for GDB on the specified port nr rather than to use a pipe to communicate with GDB. Using
tcp/ip allows to have GDB running on one computer and debugging a Valgrind process running on another target computer. Example:
# On the target computer, start your program under valgrind using
valgrind --vgdb-error=0 prog
# and then in another shell, run:
vgdb --port=1234
On the computer which hosts GDB, execute the command:
gdb prog
(gdb) target remote targetip:1234
where targetip is the ip address or hostname of the target computer.
-c
To give more than one command to a standalone vgdb, separate the commands by an option -c. Example:
vgdb v.set log_output -c leak_check any
-l
Instructs a standalone vgdb to report the list of the Valgrind gdbserver processes running and then exit.
-D
Instructs a standalone vgdb to show the state of the shared memory used by the Valgrind gdbserver. vgdb will exit after having shown
the Valgrind gdbserver shared memory state.
-d
Instructs vgdb to produce debugging output. Give multiple -d args to increase the verbosity. When giving -d to a relay vgdb, you better
redirect the standard error (stderr) of vgdb to a file to avoid interaction between GDB and vgdb debugging output.
SEE ALSO
valgrind(1), $INSTALL/share/doc/valgrind/html/index.html or http://www.valgrind.org/docs/manual/index.html, Debugging your program using
Valgrind's gdbserver and GDB[1]vgdb[2], Valgrind monitor commands[3].
AUTHOR
Philippe Waroquiers.
NOTES
1. Debugging your program using Valgrind's gdbserver and GDB
http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver
2. vgdb
http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.vgdb
3. Valgrind monitor commands
http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.valgrind-monitor-commands
Release 3.9.0 11/01/2013 VGDB(1)