kudzu at tenebras.com
Fri Jun 29 15:56:45 UTC 2018
Are there process limits?
malloc() will call abort() if internal structures are munged (e.g., by heap
calling free() on a corrupted pointer does that reliably
is the root partition big enough for the dump?
On Fri, Jun 29, 2018 at 8:40 AM, Doug Hardie <bc979 at lafn.org> wrote:
> I have a daemon process that runs forever (almost). Something is killing
> it with a signal 6, but no core dump is done. If I manually kill it with
> kill -6, then the log message shows core dumped and a core file is
> created. The process has no reference to SIG_ABRT, so I suspect the kernel
> is doing the kill and is overriding the core dump. I have previously
> encountered a similar issue where swap space was running out and the kernel
> killed this process without a core dump. In that case there were quite a
> few messages logged about swap space issues before the process was killed.
> There are no swap messages logged this time.
> /etc/sysctl.conf contains:
> /crash is a directory in the root file system.
> Other than swap issues, when would the kernel kill a process without a
> core dump?
> -- Doug
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-
> unsubscribe at freebsd.org"
"Well," Brahma said, "even after ten thousand explanations, a fool is no
wiser, but an intelligent person requires only two thousand five hundred."
- The Mahābhārata
More information about the freebsd-questions