开启Core dump调试

转自本人原先博客http://blog.sina.com.cn/s/blog_4d1bbec70100dx2l.html

运行一程序，结果可想而知，发生了段错误，在网上搜寻答案时发现，当程序dump掉以后，系统会自动生成core文件，以使用gdb -c core来进行调试。可是发生段错误：

Segmentation fault
使用：
gdb -c core来调试，系统提示
/home/yyang/core: No such file or directory.
迷茫了一段时间，然后突然醒悟。
于是采用以下命令查看：
yyang@Yanux:~$ ulimit -a
core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 2048
max locked memory       (kbytes, -l) 32
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1024
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 8192
cpu time               (seconds, -t) unlimited
max user processes              (-u) 2048
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited
才发现，core file size被限制到0了，所以dump时不产生core文件，因而无法调试，于是：
ulimit -c 1024
再次运行我的程序，看到了：
Segmentation fault (core dumped)
然后再使用gdb调试，终于成功，记录于斯：
Segmentation fault (core dumped)
yyang@Yanux:~$ gdb -c core
GNU gdb 6.8-debian
Copyright (C) 2008 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 "i486-linux-gnu".
(no debugging symbols found)
Core was generated by `p AAAAAAAAAAAAAAAAAA\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd'.
Program terminated with signal 11, Segmentation fault.
[New process 9227]
#0  0x41414141 in ?? ()
(gdb)