12-02-2010
Quote:
Originally Posted by
Learnerabc
Thanks for reply.Is it ok if I can pm you the code?
no. post it so everyone can learn.
9 More Discussions You Might Find Interesting
1. Solaris
hello ,
I have a C program which runs perfectly on linux but gives a segmentation core dump when i try to run it on solaris.
The compilation of the c code happens without any errors on solaris.
Any pointers
thanks
Nayeem (2 Replies)
Discussion started by: nayeemmz
2 Replies
2. Solaris
hi everyone,
we have solaris 8 in sun v480 server.
it gives this error.
Segmentation Fault(coredump)
can anyone help me in this - urgently.
Regards
Karthik C (8 Replies)
Discussion started by: cksriramchandra
8 Replies
3. UNIX for Dummies Questions & Answers
What's the difference between Segmentation fault and Bus error and Illegal instruction?
Sometimes I got the one, and sometimes i got another, what are their differences?
Segmentation fault (core dump)?
Bus error (core dump)?
Illegal instruction (core dump)
Thanks
Daniel (2 Replies)
Discussion started by: lakeat
2 Replies
4. UNIX for Advanced & Expert Users
Hi all,
I am trying to create few directories using script and its giving me segmentation error.
#!/bin/ksh
createDirectories()
createDirectories()
{
cat dirs | \
while read line
do
mkdir... (16 Replies)
Discussion started by: varungupta
16 Replies
5. UNIX for Advanced & Expert Users
hi all
is there any way to capture the segmentation fault error when i run sqsh on a unix shell script.
Ex:
#!/bin/ksh
sqsh -S "server" -U "user" -P "pwd" << EOF
use mydb
go
exec proc1
go
exit
EOF
retval=$?
echo "sqsh return value $retval"
if
then
exit (1 Reply)
Discussion started by: sudheer1984
1 Replies
6. Shell Programming and Scripting
Hi all,
I have a folder with some 28 files. I have a script file that will iteratively take one file at a time from the folder and provide an output for the input file. Till the 7th file, there was no problem but from the 8th file onwards, i got this Segmentation Fault(Core Dump) error. A file... (2 Replies)
Discussion started by: mick_000
2 Replies
7. Programming
Hello,
I'm experiencing a weird seg fault at run time when initializing a bi-dimensional array and initializing a class.
Please see below code and comments describing the error and the instances when it occurs and when it does not occur.
Compiled with g++ segf.cpp -o segf
output
On... (5 Replies)
Discussion started by: nmset
5 Replies
8. Programming
I use a binary name (ie polo) it gets some parameter , so for debugging normally i do this :
i wrote script for watchdog my app (polo) and check every second if it's not running then start it , the problem is , if my app , remain in state of segmentation fault for a while (ie 15 ... (6 Replies)
Discussion started by: pooyair
6 Replies
9. Programming
Hello guys, i have this code:
int main(int argc, char *argv) {
int i, j, N, result = 0, **vec;
if (argc < 2) {
fprintf(stderr, "Usage: %s N\n", argv);
}
/* ... how many numbers to read */
N = atoi(argv);
/* check if N is a power of two; exit if not */
if (!... (3 Replies)
Discussion started by: DinisR
3 Replies
tryto(1) General Commands Manual tryto(1)
NAME
tryto - tries to run a command limited by a timeout or number of tries, can be used to run as svlogd(8) processor.
SYNOPSIS
tryto [-pPv] [-t sec] [-k ksec] [-n tries] prog
DESCRIPTION
prog consist of one or more arguments.
tryto runs and watches prog, feeding its standard input to prog's standard input. If prog exits with a return code other then 0, tryto
runs prog again after sleeping one second.
If the number of retries reaches the maximal number of tries, tryto prints an error message and gives up.
If the timeout sec seconds is reached and prog is still running, tryto sends a TERM signal to prog, waits ksec seconds for prog to termi-
nate, then sends a KILL signal if prog still is there, and exits as soon as possible.
OPTIONS
-t sec timeout. Set the timeout to send TERM to prog to sec seconds. Default is 180.
-k ksec
kill timeout. Set the timeout to send KILL to prog to ksec seconds. Default is 5.
-n tries
Set the maximal number of tries to tries. If prog exited with a return code other that 0, tryto tries to rewind standard input to
the beginning using lseek(2) before starting prog again. Default is 5.
-p processor. Use this option if you run tryto as a svlogd(8) processor (see below).
-P process group. Run prog in a new session and process group, and send signals on timeout to prog's process group instead of its pid.
-v verbose. Print verbose messages to standard error.
PROCESSOR
If tryto sees the -p option, tryto runs as a svlogd(8) or multilog(8) processor, making use of filedescriptors 4 and 5:
Before starting prog, tryto moves the filedescriptor 5 to 2, so all error messages from tryto and prog will be saved in svlogd(8)'s state
to be processed on the next run of tryto -p.
After starting prog, tryto first feeds all data it reads from filedescriptor 4 into prog's standard input, then all data from filedescrip-
tor 0.
If prog fails by timeout sec seconds or maximal number of tries, tryto prints all data from standard input to standard output, an error
message to standard error, and exits with 0.
EXIT CODES
If tryto itself fails, it returns 111.
If tryto runs as a svlogd(8) processor, tryto returns 0 in all other cases.
If prog was run successfully, tryto returns 0.
If prog failed by timeout, tryto returns 100.
If prog failed by maximal number of tries, tryto returns the last return code from prog.
SEE ALSO
socklog(8), uncat(1), svlogd(8), multilog(8), lseek(2)
http://smarden.org/socklog/
http://smarden.org/runit/
AUTHOR
Gerrit Pape <pape@smarden.org>
tryto(1)