01-22-2009
Gdb
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.
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. HP-UX
Hi,
I'm trying to debug my gcc compiled code on my HPUX 11.23 (Itanium).
I searched the machine to find something that looks like a compiler, and what I found was :
adb (a bit unfriendly for debugging)
kwdb (I understand this is a kernel debugger)
gdb32
gdb64
gdbpa
When I run either... (0 Replies)
Discussion started by: rimon
0 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 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
KGDB(1) BSD General Commands Manual KGDB(1)
NAME
kgdb -- kernel debugger
SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]]
DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files.
The options are as follows:
-a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful
when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well.
-b rate Set the baudrate to rate.
-q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well.
-v Increase verbosity.
-w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for
FreeBSD.)
-d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will
be appended to determine the actual dump file name.
-c core Explicitly use core as the core dump file.
-n dumpnr Use the kernel core dump file numbered dumpnr for debugging.
-r device Use device to connect kgdb to for a remote debugging session.
The -c, -n, and -r options are mutually exclusive.
Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu-
ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has
been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run-
ning kernel.
FILES
/dev/mem Default memory image to open if no core dump file has been specified.
/var/crash Default directory to locate kernel core dump files.
SEE ALSO
gdb(1)
HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3.
BSD
October 11, 2006 BSD