CoreDump analyse

1 Found core dump files：

-rw------- 1 root root 1019645952 Dec 14 01:56 core.7002
-rw------- 1 root root 1020059648 Dec 14 01:56 core.7156
-rw------- 1 root root 924336128 Dec 14 01:56 core.7333
-rw------- 1 root root 525479936 Dec 14 01:56 core.7510
-rw------- 1 root root 945373184 Dec 14 02:01 core.8106
-rw------- 1 root root 882405376 Dec 14 02:01 core.8259
-rw------- 1 root root 935002112 Dec 14 02:01 core.8412
-rw------- 1 root root 945262592 Dec 14 02:01 core.8560
-rw------- 1 root root 514748416 Dec 14 02:01 core.8721
-rw------- 1 root root 945479680 Dec 14 02:01 core.8827
-rw------- 1 root root 588562432 Dec 14 02:01 core.8976
-rw------- 1 root root 934895616 Dec 14 02:01 core.9101
-rw------- 1 root root 567263232 Dec 14 02:01 core.9271
-rw------- 1 root root 956264448 Dec 14 02:01 core.9400

2 file （Use command file to identify file type and found the process name which born this coredump）

[root@premta tmp]# file ./core.7002
./core.7002: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from ‘bin/httpserver‘

3 GDB

　　gdb httpserver /tmp/core.6852

4 ps

　　the so need with debug info,so in private env you could compile code with -g param,in prod,you cloud attache the debug-info build with the same build,they could work well(no need to compile again and wait the coredump happend again).

CoreDump analyse

原文：http://www.cnblogs.com/dogharry/p/5044366.html