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）

[[email protected] 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).

时间： 2024-12-04 17:49:28

CoreDump analyse的相关文章

《coredump问题原理探究》Linux x86版6.3节有成员变量的类coredump例子

在探究完类成员变量分布后,来定位一个coredump例子来实践一把: (gdb) bt #0 0x0804863c in xuzhina_dump_c06_s2_ex::print() () #1 0x08048713 in main () 看一下xuzhina_dump_c06_s2_ex::print的汇编: (gdb) disassemble 0x0804863c Dump of assembler code for function _ZN22xuzhina_dump_c06_s2_ex

Linux下产生coredump并压缩保存

设置coredump大小为'无限'ulimit -c unlimited 开启coredump记录进程号echo "1" > /proc/sys/kernel/core_uses_pid 指定coredump路径echo "/home/panchen/core-%e-%p-%t"> /proc/sys/kernel/core_pattern 压缩coredumpcat /usr/local/sbin/core_helper #! bin/shexec g

segv & mini coredump

1. mini coredump a. segv http://zh.scribd.com/doc/3726406/Crash-N-Burn-Writing-Linux-application-fault-handlers https://github.com/gby/libcrash b. /proc/PID/coredump_filter http://stackoverflow.com/questions/8836459/minimal-core-dump-stack-trace-curr

《coredump问题原理探究》Linux x86版6.8节多继承coredump例子

下面看一个coredump的例子: (gdb) bt #0 0x08048662 in xuzhina_dump_c06_s5_ex_child::inheritFrom(char*, int) () #1 0x08048609 in main () 先看一下xuzhina_dump_c06_s5_ex_child::inheritFrom的汇编: (gdb) disassemble 0x08048662 Dump of assembler code for function _ZN28xuzh

coredump查原因

1. dmesg |tail -n 1 2. objdump -DCI ./a.out 示例: $ cat a.cpp #include <stdio.h> int main(){ int *pa=NULL; *pa=0; return 0;} $ g++ -g a.cpp $ ./a.out Segmentation fault $ dmesg | tail -n 1[49481461.465836] a.out[17960]: segfault at 0 ip 00000000004005

coredump简介与coredump原因总结

from:http://www.cnblogs.com/doctorqbw/archive/2011/12/21/2295962.html 千兵卫博士 coredump简介与coredump原因总结 什么是coredump? 通常情况下coredmp包含了程序运行时的内存,寄存器状态,堆栈指针,内存管理信息等.可以理解为把程序工作的当前状态存储成一个文件.许多程序和操作系统出错时会自动生成一个core文件. 如何使用coredump? coredump可以用在很多场合,使用Linux,或者sol

《coredump问题原理探究》Linux x86版7.4节List coredump例子

看一个coredump例子: 看一个coredump例子: Core was generated by `./xuzhina_dump_c07_s2_ex'. Program terminated with signal 11, Segmentation fault. #0 0x0285b9b7 in std::_List_node_base::hook(std::_List_node_base*) () from /usr/lib/libstdc++.so.6 Missing separate

Memory Analyse Tool

Memory Analyse Tool(MAT) 1: export .hprof file ADT>DDMS>Dump HPROF file 2: convert to standard format use HPROF Converter tool provided in android sdk. The hprof-conv tool converts the HPROF file that is generated by the Android SDK tools to a stand

《coredump问题原理探究》Linux x86版6.5节虚函数的coredump例子

在大型项目中,很容易出现版本不匹配的问题,其中导致的虚函数飘移的问题比较难解决. 在这里,用一个例子来说明如何解决这种问题. 建立三个源文件:testso.h,testso.cpp,xuzhina_dump_c6_s3_ex.cpp. testso.h的代码如下: 1 #ifndef __TESTSO_H__ 2 #define __TESTSO_H__ 3 4 class xuzhina_dump_c6_s3_ex 5 { 6 public: 7 virtual char* encode( c