Gdb error while debugging core file Post: 302891737

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Using GDB to analyse different CORE dumps

Hi, Can we modify the GDB source code so as to analyze core dumps from different targets? From my analysis, I think we need to build our section table statically for each target. i.e., including the various address boundaries in build_section_table() function. If this is the case, then the GDB...

2. Programming

Debugging 64bit code with gdb and ddd in AIX

I'm trying to use the GDB debugger and DDD to debug 64bit code. It seems that the AIX toolkit gdb version 6.0 works with 64bit code. But the ddd tool when running gdb gives the following errors : Starting program: <my binary> <my params> warning: "": not in executable format: There is an input...

3. UNIX for Dummies Questions & Answers

Debugging core file from another server

Hi all, One fine day one of the services in our prod server started core dumping and then the core file was ftp'd to our test server , to debug we used gdb with the executable which we had but we could not get the function names ( maybe due to missing symbols ) How do i solve this ...

4. Programming

Debugging a running process in GDB

Hi , Any gdb user could see my problem. Let me describe what i want to do. i have a test utility to send message to running process. My interest is to go through to functions calls when my test case starts. In a simple way i want have a code walk for a particular scenario of a test...

5. Linux

unable to read core dumps on unix. Is there another way than using GDB?

hi all, I am having set of core dumps obtained from client server. Now i am trying to read them but unable to do so. I have few queries: 1. Core dumps were generated on some xyz server and copied to my unix virtual. Can I read them as text here? 2. I tried installing gdb-7.3 but when i fire...

6. UNIX for Dummies Questions & Answers

GDB Debugging Problem

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...

7. Programming

64 bit code debugging using gdb and ddd

Hello I have built our application on AIX 7.1 as a 64 bit application. My queries are as follows: Can a 32bit gdb (v7.6) and ddd (data display debugger - v3.3.12), debug a 64bit executable ? If I have a small 64bit a.exe executable that seems to work. If I have a more complicated executable...

8. Programming

Best guide or video for gdb <register level debugging>

would like to know best guide or document for gdb for different architectures x86 , power pc etc.. would like to understand how to debug segmentation faults because of stack corruption .. understand utilities ELF , objdump etc.. please guide me

9. Programming

Best reference for understanding core file and debugging for different architectures

Hi , could someone suggest best reference for core file understanding , analysis , debugging for different architectures like what registers represent what in a architecture specific core .. how to get maximum information out of corrupted core different tools and how they work and how to...

LEARN ABOUT FREEBSD

crashinfo

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