How to know which binary generated obtained core dump?

10 More Discussions You Might Find Interesting

1. Solaris

core dump

Hi guys, just want to know which core file pattern is best to set for core dumps: 1) per-process file name pattern or 2) global file name pattern. I will really appreciate an explanation why the chosen one is better. Thanks a lot guys.

2. Programming

which binary dumped core dump?

I have discovered a large number of core dumps on one of our OSX machines (dumped into a generic /cores dir). Is there any way to find out which binary generated them? Thanks!

3. Linux

Core file not getting generated!!

Some strange behavior. Process is receiving Segmentation Fault. But no core files getting generated. I have checked ulimit. coredumpsize = unlimited. In console, process is printing Segmentation Fault even through gdb also same behavior But No corefile. Any possible reason ? ...

4. Solaris

core files not getting generated

Hi, We have an application ASPA . The application related processes are running in /ASPA/bin directory . now whenever a process terminates abruptly , a core file should be generated (correct me if i am wrong) in the /ASPA/bin directory . But i am not able to see any such files . The...

5. Programming

core dump

how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace.

6. UNIX for Advanced & Expert Users

Core Dump

Hello all, Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time...

7. Programming

about core dump

MY friends: my program under sco unix have a problem? it create a core dump file on the path when execute program , but i can't find the error of the C program ,i don't know how to see the error about my program use core, please help me or give me some suggest and what tools can use...

8. Programming

Core File Not Being Generated in AIX

I have created an executable using my login session in an AIX Version 5 Unix system. After to which I have change the file mode to set uid and rwsrwx--x and ownership to root:system by using the following Standard C Library functions. chmod (name, S_ISUID|S_IRWXU|S_IRWXG|S_IXOTH|S_IROTH) chown...

9. UNIX for Dummies Questions & Answers

core dump

I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start but savecore failed to create the two files, that is vmcore.n and vmunix.n. savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname 1)...

10. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

LEARN ABOUT FREEBSD

kgdb

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

Programming