Solaris Core Dump Analysis
I use pstack to analyze core dump files in Solaris
How else can I analyze the core dump from solaris?
What commands can be used to do this?
What other information will be available from the dump?
You can use Solaris modular debugger,mdb, or dbx. mdb comes with SUNWmdb (or SUNWmdb x for the 64 bits version) package.
A core file is the image of your running process at the time it crashed.
Depending on whether your application was compiled with debug flags or not,you will be able to view an image of the stack, hence to know which function caused the core, to get the value of the parameters that were passed to that function, the value of the variables, the allocated memory zones ...
On recent solaris versions, you can configure what the core file will contain with the coreadm command ; for instance, you can have the mapped memory segments the process were attached to.
- → Interbase xe7 - cannot restore
- → How can i access the value of a ruby array in C? (editing array.c:rb_ary_initialize from ruby source code)
- → Is it possible to get a core dump of a running process and its symbol table?
- → Questions about CUDA macro __CUDA_ARCH__
- → Line number of segmentation fault
- → Debugging a segmentation fault when I do ctrl c
- → ARM64 Buffer Overflow-Cannot overwrite $pc
- → argc is always zero
- → Convert assembly instructions to bytes in gdb
- → Is it possible to use executables having no debug symbols with valgrind?
- → Overflowed bytes different than those I see on GDB?
- → Opposite of a Heisenbug, segmentation fault that appear ONLY when debugging, but program works fine
- → lockf.c: No such file or directory