Date: Wed, 20 Jan 2010 13:05:09 -0800 From: Chuck Swiger <cswiger@mac.com> To: Doug Poland <doug@polands.org> Cc: questions Questions <questions@freebsd.org> Subject: Re: Trouble getting a core dump from clamd Message-ID: <ED733F36-49ED-4FFA-B0D2-4BE90CDA9FE7@mac.com> In-Reply-To: <0cc4c74334a73d21b31ad06d41e3779a.squirrel@email.polands.org> References: <db60663b086aed5329984a666b8b7e08.squirrel@email.polands.org> <d36406631001190910g5c56b43en9ca9b87bf244a40d@mail.gmail.com> <a3de0a40551edaedbb49b1d5ac2366a2.squirrel@email.polands.org> <6C738BD4-71EE-4F34-8DB5-ABDB45A06C89@mac.com> <0cc4c74334a73d21b31ad06d41e3779a.squirrel@email.polands.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi--
On Jan 20, 2010, at 12:46 PM, Doug Poland wrote:
> Thanks for the suggestion and the pointer to man 5 core. I
> implemented your suggestions but still get no core dump. Very
> strange...
Check your default resource limits (shell startup files & /etc/login.conf) and see whether coredumpsize is set to 0, maybe? If you build and run:
% cat crash.c
#include <stdlib.h>
main()
{
char *bad = NULL;
bad[0] = '1';
}
% cc -o crash crash.c
% ./crash
[1] 16550 segmentation fault (core dumped) ./crash
% ls /cores
crash.16550.core
...do you get this trivial program to dump core?
Regards,
--
-Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ED733F36-49ED-4FFA-B0D2-4BE90CDA9FE7>