10-15-2003
gdb command
I'm having problem understanding the how to use gdb command to debug my program. Can anyone give me some suggestion how to start, and examples. I read the manual in unix...I'm still confuse.
10 More Discussions You Might Find Interesting
1. Programming
Which is better??
I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it???
:cool: (1 Reply)
Discussion started by: jyotipg
1 Replies
2. Programming
Can anyone give me the link to a website having gdb tutorials
(for advanaced debugging & shortcuts)
http://www.burneddowndays.com/talk/YaBBImages/rolleyes.gif (1 Reply)
Discussion started by: wojtyla
1 Replies
3. Programming
If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see:
run:
./executablefile1 agr1 arg2 arg3
debug:
gdb executablefile1
run executalbefile1 arg1 arg2 arg3
then argv : executablefile1
argv : executablefile
argv : arg1
... (3 Replies)
Discussion started by: cdbug
3 Replies
4. UNIX for Advanced & Expert Users
Hi,
This is a simple question on GDB. Given a core file, how can you check which process has dumped the core?
Regards
- Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I wanted to know if there is a core file generated and I am not sure for which Binary it is generated .
Can I use gdb to debug the core file ?
Thanks. (1 Reply)
Discussion started by: shubhranshu
1 Replies
6. UNIX for Advanced & Expert Users
Hi All,
I am trying to execute a binary and it is giving Segmentation Fault.
Can I use gdb to debug this error?
Secondly there is no core file generated , so when I an trying to run gdb with the binary only I am not able to set any breakpoints.
When I am running the gdb and the I am... (1 Reply)
Discussion started by: shubhranshu
1 Replies
7. Programming
Hello,
I am having problem with debugging my code. I am writing a C code and then I compile it with the Makefile. I make a target file and then copy it in my Robot(Khepera III) and then run the program over there.
I compile it ofcorse on my machine and then copy the compiled file in the... (10 Replies)
Discussion started by: mind@work
10 Replies
8. Programming
i have created some break points in gdb.
let's say....
b sqlcxt
how can i know the breakpoint name of sqlcxt ??? (1 Reply)
Discussion started by: lipun4u
1 Replies
9. Programming
Hi, I got:
host machine: RedHat (RHEL6)
virtual machine: RedHat (RHEL6)
I run (on host machine):
qemu-system-x86_64 ...... -S -s
after that i run (on host machine):
gdb
target remote localhost:1234
set architecture i386:x86-64
and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies
10. Programming
Hi, all
I try to understand the output from gdb
Program received signal SIGABRT, Aborted.
*** glibc detected *** /home/sys_cbo/dev/zif/bin/Debug/zifd: free(): invalid pointer: 0x00007fffac04d3d0 ***
how should i read this?
(gdb) backtrace
#0 0x0000003015e32925 in raise () from... (1 Reply)
Discussion started by: huvcbo
1 Replies
LEARN ABOUT CENTOS
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)