Hi,
I have got core dump stating "core.bash.29846" so i am unable to open.
How to open the core dump file for further analysis?
Reagards
Vanitha
Please check below links:
Basic Info:
Core Dump Management on the Solaris OS
Using mdb:
http://download.oracle.com/docs/cd/E19082-01/817-2543/
http://www.cuddletech.com/blog/pivot/entry.php?id=965
Using Solaris CAT:
http://www.cuddletech.com/blog/pivot/entry.php?id=966
Using dbx:
http://download.oracle.com/docs/cd/E19422-01/819-3683/
use string command to read all string from core and redirect it to some tmp file.
if you are using solaris, then refer the below commands
dbx
pstack
mdb
This is not the proper way to debug a core file. use a debugger like already suggested.
If you have a core file and you have compiled the program with debuging options (-g), you can see where the core was dumped:
$ gcc -g -o something something.c $ ./something Segmentation fault (core dumped) $ gdb something core You can use this to do some post-mortem debuging. A few gdb commands: br prints the stack, fr jumps to given stack frame (see the output of br).
Now if you want to see which files are opened at a segmentation fault, just handle the SIGSEGV signal, and in the handler, just dump the contents of the /proc/PID/fd directory (i.e. with system('ls -l /proc/PID/fs') or execv).
With these informations at hand you can easily find what caused the crash, which files are opened and if the crash and the file descriptor leak are connected.
Visit : Core Dump Error in Linux: core.bash.29846 - Techyv.com
1 Like
From man core(5):
You can send a process (via the kill command) any of the signals whose corresponding action is "core" listed in that man page. This includes:
SIGQUIT, SIGILL, SIGABRT, SIGFPE, SIGSEGV, SIGBUS, SIGSYS, SIGTRAP, SIGXCPU, SIGXFSZ, SIGIOT,
The catch is that (1) a process can choose to ignore these signals or handle them without doing a core dump, and (2) the parent shell can limit the core dump through ulimit or other commands.