Live data from Hacker News

Don't Leave Coredumps on Web Servers

blog.hboeck.de

1–10 of 34 posts

Re: Don't Leave Coredumps on Web Servers

#6
post #4

You can "Control + \" your application to generate a core dump if you want to test it.

It didn't work for me on macOS. I tried it on `yes` and `sleep 5` but it simply quit the program. No files were saved.

It is possible to set a maximum size for core dump files via limits.conf / ulimit. If this limit is 0, it effectively disables core dumps. Call ulimit -a from a shell to see the current maximum size.

The linked article also explains how to change where core dumps are saved. Maybe your system is configured to save them in a specific folder (I have no clue what macOS' default settings for core dumps are!).

Re: Don't Leave Coredumps on Web Servers

#8
post #6
post #4

Earlier quoted context omitted.

It didn't work for me on macOS. I tried it on `yes` and `sleep 5` but it simply quit the program. No files were saved.

It is possible to set a maximum size for core dump files via limits.conf / ulimit. If this limit is 0, it effectively disables core dumps. Call ulimit -a from a shell to see the current maximum size. The linked article also explains how to change where core dumps are saved. Maybe your system is configured to save them in a specific folder (I have no clue what macOS' default settings for core dumps are!).

I have a mac, and my default settings are a ulimit of zero. Makes sense, because macOS has its own way of creating crash reports with the CrashReporter daemon
Post reply on HN