UNIX for Dummies Questions & Answers

my progrme complaints 'Segmentation fault'.
How to let it print 'Segmentation fault(core dumped)' and generate core dump file?

Code:

$ulimit
unlimited

Well, you have not told us what type of system you are on - so it is difficult to give a definitive answer.

Assuming you are on a GNU/Linux system., then enter

Code:

ulimit -c unlimited

Also, when you cannot write to the current directory, no core is written. Does your program call chdir()? Try looking there as well.

I used to run a cron script to find core files, generate reports on them (stack trace if possible, ownership or file output at least), save them in /tmp compressed (in case they are important and might get overwritten), and email the report to the dev group. People write a lot of unattended scripts with loose error checking, and a core report may raise awareness of a hole in the code or why a periodic process has no effect. So, search everywhere for a file called core, run it through ls -l and file, and see what has been dying! Also, do not run code in unwritable directories if you want a core.

The cd is much overused in the popular UNIX pragma. There are lots of ways to handle paths without $PWD, like X cut/paste and command recall. It makes shell command history less useful! Life is simpler if you stay home most of the time!

I am using ArchLinux2.6.33.
I write the program, and it runs on my home dir.

it as simple as this:

Code:

  1 int main()
  2 {
  3         char *p="abc";
  4         p[0]='a';
  5 }

I wrote it just want to test core dump.

Seems legal! You can test core with kill -10 or the like on anything that sits still long enough.

Cell likes to duplicate, sorry.