以下是小可关于coredump的理解有不对之处希望大家指正
简单的崩溃可以 通过日志和堆栈信息定位
复杂的则需要借助 coredump 文件定位
coredump调试步骤如下
写入测试程序
vim test.c
#include <stdio.h>
#include <string.h>
int main()
{
int *ptr = NULL;
*ptr = 10;
return 0;
}
编译并执行
在程序启动时打开coredump,并设置coreduump存储路径为可执行文件所在路径
gcc -g test.c -o test
ulimit -c unlimited
echo "core.%e" > /proc/sys/kernel/core_pattern
./test
gdb调试
gdb ./test core.test.30489
结果如下
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-120.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /root/test...done.
[New LWP 30489]
Core was generated by `./test'.
Program terminated with signal 11, Segmentation fault.
#0 0x00000000004004fd in main () at test.c:8
8 *ptr = 10;
Missing separate debuginfos, use: debuginfo-install glibc-2.17-323.el7_9.x86_64
(gdb)
由此看出崩溃是在test.c第8行