使用GDB根据段错误core dump文件定位问题

最新推荐文章于 2026-02-27 01:55:53 发布

原创最新推荐文章于 2026-02-27 01:55:53 发布 · 478 阅读

0 ·

本内容遵循CC 4.0 BY-SA版权协议

收录于

Linux 应用程序编程

当前文章被收录于：

Linux 应用程序编程

142 篇文章 7 人学习

订阅专栏查看详情

当前文章被以下社区和专栏收录：

本文介绍使用GDB工具根据段错误coredump文件定位问题的具体步骤。通过实例演示，从生成段错误到利用GDB读取core文件，最终定位到出错的代码行，帮助开发者快速解决内存访问错误。

使用GDB根据段错误core dump文件定位问题

#include <stdio.h>
int main(void)
{
    char *s = "hello world";
    *s = 'H';
}

$ gcc segfault.c -g -o segfault
$ ./segfault
Segmentation fault

来自：https://en.wikipedia.org/wiki/Segmentation_fault

如何定位

$ gdb-multiarch ./segfault core
GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Copyright (C) 2018 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-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./segfault...done.
[New LWP 26596]
Core was generated by `./segfault'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000564dbceae76e in main () at segfault.c:19
19	    *s = 'H';
(gdb)

这样就定位到具体出错的行了。