标签:style blog http color os io ar for 2014
We can get SegFault by several reasons:
cross-border access
int temp[2] = {0}; temp[2] = 2; // SegFault
write on read-only access
char *temp = "Haha"; temp[1] = 2; // SegFault
DEBUG flavour usually add some assert() statements about the memory alignment access.
If DEBUG flavour did not give any assert report, or you have fixed all the assert() report, but it still aborts with SegFault. What‘s next?
Usually, we can add "-g" compiler flag and rebuild the executable, then use gdb to locate where is the SegFault.
then with gdb:
$ gcc -g -O3 main.c segfault.c -o segfault.x $ gdb ./segfault.x GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. (gdb) r Starting program: /home/jxion/jxion_porting_server/users_jxion/test_segfault/segfault.x Test for SegFault. Program received signal SIGSEGV, Segmentation fault. f0 () at segfault.c:6 6 tmp[0] = ‘h‘; (gdb) bt #0 f0 () at segfault.c:6 #1 0x0000000000400557 in f1 () at main.c:19 #2 0x000000000040058b in f2 () at segfault.c:12 #3 0x0000000000400567 in f3 () at main.c:24 #4 0x000000000040059b in f4 () at segfault.c:17 #5 0x00007ffff7a35ec5 in __libc_start_main (main=0x400440 <main>, argc=1, argv=0x7fffffffd6f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd6e8) at libc-start.c:287 #6 0x0000000000400482 in _start () (gdb)
Now you can get all info you need.
[SegFault] 讨厌的段错误 how to debug "Segment Fault" on Linux
标签:style blog http color os io ar for 2014
原文地址:http://www.cnblogs.com/xjsxjtu/p/3958390.html