09-24-2010
So you copy the executable file to the robot, and run the debugger on the robot? Can you ldd filename on the robot to see if there's perhaps any shared libraries missing, etc?
You should be able to gdb anything, though symbols may not be available for proprietary things not built with debugging support.
"no executable file specified" is an odd error. Are you specifying the file on the commandline? "gdb ./filename", not just "gdb"? Sometimes weird error messages can happen from dynamic link problems, but...
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
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. (6 Replies)
Discussion started by: Confuse
6 Replies
3. Shell Programming and Scripting
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Discussion started by: umen
2 Replies
4. Solaris
I want to install gdb on SunOS 5.6 machine. Where can i download from ? (1 Reply)
Discussion started by: shafi2all
1 Replies
5. 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
6. 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
7. 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
8. UNIX for Advanced & Expert Users
Hi all
What 's the relationship between gdb and ptrace, if the kernel does
not support ptrace, can gdb work ?
Is there some one can explain this for me (3 Replies)
Discussion started by: yanglei_fage
3 Replies
9. 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
10. 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
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)