05-30-2008
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
If we want to debug a shell script, then set -vx has to be included in the begining of the script. Just i want to know what purpose -vx is used.
Thanks in advace
Sarwan (2 Replies)
Discussion started by: sarwan
2 Replies
2. UNIX for Advanced & Expert Users
Can anyone tell the commands we use for debugging a programm in dbx with explanation for each?
Iam totally new to unix environment (3 Replies)
Discussion started by: bogarams
3 Replies
3. Solaris
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)
Discussion started by: satish@123
0 Replies
4. Programming
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)
Discussion started by: ps_sach
5 Replies
5. UNIX for Dummies Questions & Answers
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)
Discussion started by: pratibha
0 Replies
6. Programming
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)
Discussion started by: gotenxds
2 Replies
7. Shell Programming and Scripting
Hi
i was going through the script debugging technique. below example was given in the book.
1 #!/bin/sh
2
3 Failed() {
4 if ; then
5 echo "Failed. Exiting." ; exit 1 ;
6 fi
7 echo "Done."
8 }
9
10 echo "Deleting old backups,... (11 Replies)
Discussion started by: scriptor
11 Replies
8. UNIX for Dummies Questions & Answers
I have added some code in my file.
I have created executable rpm file of our code and also I have created debuginfo and debugsource files and installed all three.
But when I debug in gdb I see the the code changes in soucre file. But the break point does not hit at that place as if it did not... (1 Reply)
Discussion started by: rupeshkp728
1 Replies
9. Shell Programming and Scripting
the attached perl script is a deamon that, once kicked off from the command line, it runs in the background and waits for the master server to tell it what plugins to run.
the script works well. but the problem is, whenever i start it, after about a few seconds of starting it, i start getting... (4 Replies)
Discussion started by: SkySmart
4 Replies
LEARN ABOUT DEBIAN
btraceback
BTRACEBACK(1) Network backup, recovery and verification BTRACEBACK(1)
NAME
btraceback - wrapper script around gdb and bsmtp
SYNOPSIS
btraceback /path/to/binary pid
DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.
USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur-
rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).
NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.
Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse-
quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.
ENVIRONMENT
btracback relies on $PATH to find the debugger.
FILES
/usr/lib/bacula/btraceback
The script itself.
/usr/sbin/btraceback
symbolic link to /usr/lib/bacula/btraceback
/etc/bacula/scripts/btraceback.gdb
the GDB command batch used to output a stack trace
AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>
SEE ALSO
bsmtp(1)
Kern Sibbald 6 December 2009 BTRACEBACK(1)