Core dump file not generated on segmentation fault

c linux gdb coredump
Tim picture Tim · Oct 16, 2010 · Viewed 24.3k times · Source

I am trying to debug a segmentation fault caused by my C program using gdb. A core dump file is not automatically generated when I run my program,and i have to run the command 

ulimit -c unlimited

for a core file to be generated on the next run.

Why is a core dump file not generated automatically and why do I have to run the ulimit command everytime to generate a core file on the next run of my program ?.

The operating system i use is Ubuntu 10.10.

Answer

Michalis Giannakidis picture Michalis Giannakidis · Oct 16, 2010

You need to place the command 

ulimit -c unlimited

in your environment settings.

If you are using bash as your shell, you need to place the above command in ~/.bashrc

Related questions

GDB and trouble with core dumps

Meet my $ uname -a Linux hostmachine 4.1.2-2-ARCH #1 SMP PREEMPT Wed Jul 15 08:30:32 UTC 2015 x86_64 GNU/Linux I'm trying to learn how to use GDB for debugging C programs. I think it would be particularly excellent if I could use GDB …

Read More
How do I pass a command line argument while starting up GDB in Linux?

I have to debug a program that has errors in it as part of my assignment. However, I must first pass command line arguments in order to solve this problem. I do: gdb -tui InsertionSortWithErrors which works, but after that …

Read More
How to modify memory contents using GDB?

I know that we can use several commands to access and read memory: for example, print, p, x... But how can I change the contents of memory at any specific location (while debugging in GDB)?

Read More