Sponsored Content
Full Discussion: Gdb
Top Forums UNIX for Advanced & Expert Users Gdb Post 302279116 by vino on Thursday 22nd of January 2009 02:31:25 AM
Old 01-22-2009
Quote:
Originally Posted by shubhranshu
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.
You can use gdb to debug the core file. If you want to know which binary created the core file, use
Code:
file <core-file-name>

 

10 More Discussions You Might Find Interesting

1. Programming

GDB or DBX??

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

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. (6 Replies)
Discussion started by: Confuse
6 Replies

3. HP-UX

gdb for HPUX 11.23

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

gdb for SunOS 5.6

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

Gdb:

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

Using Gdb

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

gdb not found

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

gdb help

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

Qemu + gdb

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

Gdb backtrace

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
CRASHINFO(8)						    BSD System Manager's Manual 					      CRASHINFO(8)

NAME
crashinfo -- analyze a core dump of the operating system SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core] DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX. By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel file can also be explicitly provided via the kernel argument. Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8), ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8). The options are as follows: -d crashdir Specify an alternate core dump directory. The default crash dump directory is /var/crash. -n dumpnr Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory. -k kernel Specify an explicit kernel file. SEE ALSO
textdump(4), savecore(8) HISTORY
The crashinfo utility appeared in FreeBSD 6.4. BSD
June 28, 2008 BSD
All times are GMT -4. The time now is 03:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy