OS : SOLARIS 10
debug tool :$gdb -v
GNU gdb 6.6
compiler : $gcc -v
gcc version 2.95.3 20010315 (release)
When i tried to debug my application i got the following error.
$gdb Pal
GNU gdb 6.6
Copyright (C) 2006 Free Software Foundation, Inc.
This GDB was... (2 Replies)
when I tried to debug my application i got the following.
gdb -v
GNU gdb 6.6
file is in C and Xmotiff Languages
(gdb) attach 25499
Attaching to process 25499
Retry #1:
Retry #2:
Retry #3:
Retry #4:
0xfea40b68 in ?? ()
(gdb) where
#0 0xfea40b68 in ?? () (0 Replies)
Hi i want to debug the C program with GDB debugger. I want to debug the program by line by line. I want to debug program like as we debug the program in Turbo-C using the F8. Can any one help me?
I know i have to use single stepping. But i don't know how to use it. Any help can be appreciated..... (5 Replies)
is there any way you can add a breakpoint in a script so you can stop on it?
i have used -xv in my shebang but the script just runs and i want it to stop at a specific point in the script.
appreciate any help. (1 Reply)
hi all, would you please help me correcting and debugging this script: fx-permiss.sh which accepts a list of users as argument resiting those files permissions:
say our directory structure:
/home/erzal/file
/home/erzal/dire
/home/erzal/share
/home/erzal/share/file
/home/erzal/share/dire
1-... (1 Reply)
School:Syrian Virtual University - Bachelor in Information Technology - Tutor: A.Issa - course: S10-iti320
hi all, would you please help me correcting and debugging this script: fx-permiss.sh which accepts a list of users as argument resiting those files permissions:
say our directory... (0 Replies)
hey,
can any one please tell me how can i debug blcr??
actually i have checkpointd a client using blcr and i want to check out what actually happens when we checkpoint any program. so i want to see what happen when we type
$cr_checkpoint pid
i mean i want to debug when i enter this... (0 Replies)
hey
i have a problem with a switch case in program and the debugger is messy has hell ( we use normal VI and gdb in our schoool to make it more diffiacult)
any way i have a problom where for some unknown reason the debugger just skips a switch statment as if it wasent even there
the rest... (2 Replies)
So here I have a simple function that I wish to debug. However, I am unable to debug the desired function even with set -o functrace enabled. Before resorting to asking this question, I had managed to find a possible solution that did not produce the desired results, which is located here.
How... (5 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
I am VERY much a neophyte with shell scripting. I am working on the following,
1. The problem statement, all variables and given/known data:
"Create a script sends an... (7 Replies)
Discussion started by: doghouse308
7 Replies
LEARN ABOUT ULTRIX
exec
exec(1) User Commands exec(1)NAME
exec, eval, source - shell built-in functions to execute other commands
SYNOPSIS
sh
exec [argument...]
eval [argument...]
csh
exec command
eval argument...
source [-h] name
ksh
*exec [arg...]
*eval [arg...]
DESCRIPTION
sh
The exec command specified by the arguments is executed in place of this shell without creating a new process. Input/output arguments may
appear and, if no other arguments are given, cause the shell input/output to be modified.
The arguments to the eval built-in are read as input to the shell and the resulting command(s) executed.
csh
exec executes command in place of the current shell, which terminates.
eval reads its arguments as input to the shell and executes the resulting command(s). This is usually used to execute commands generated as
the result of command or variable substitution.
source reads commands from name. source commands may be nested, but if they are nested too deeply the shell may run out of file descrip-
tors. An error in a sourced file at any level terminates all nested source commands.
-h Place commands from the file name on the history list without executing them.
ksh
With the exec built-in, if arg is given, the command specified by the arguments is executed in place of this shell without creating a new
process. Input/output arguments may appear and affect the current process. If no arguments are given the effect of this command is to mod-
ify file descriptors as prescribed by the input/output redirection list. In this case, any file descriptor numbers greater than 2 that are
opened with this mechanism are closed when invoking another program.
The arguments to eval are read as input to the shell and the resulting command(s) executed.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
EXIT STATUS
For ksh:
If command is not found, the exit status is 127. If command is found, but is not an executable utility, the exit status is 126. If a redi-
rection error occurs, the shell exits with a value in the range 1-125. Otherwise, exec returns a zero exit status.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO csh(1), ksh(1), sh(1), attributes(5)SunOS 5.10 17 Jul 2002 exec(1)