bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: need explanation ulimit -c for limiting core dumps


From: Matthew Woehlke
Subject: Re: need explanation ulimit -c for limiting core dumps
Date: Fri, 20 Oct 2006 17:55:36 -0500
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0

Chet Ramey wrote:
address@hidden wrote:
I'm trying to limit the size of coredumps using 'ulimit -c'.  Can
someone please explain why a core file gets generated from the coretest
program (source is below)?

Thanks for any help or suggestions.

% ulimit -H -c
512
% ./coretest 2048
rlim_cur,rlim_max = 524288,524288
malloced 2097152 bytes my pid is 21255
Segmentation fault (core dumped)
% ls -l core
-rw-------  1 jacr swdvt 2265088 2006-10-19 14:24 core

Are you sure that's not an old core file?  My Linux testing indicates that
the coredump bit is set in the exit status, but no core file is actually
created:

$ ulimit -c 512
$ ./xcore 2048
rlim_cur,rlim_max = 524288,524288
malloced 2097152 bytes my pid is 7661
Segmentation fault (core dumped)
$ ls -ls core
/bin/ls: core: No such file or directory

You sure your Linux makes 'core' and not 'core.<pid>', right? You might want to do 'ls -ls core*' instead...

$ ls core*
ls: core*: No such file or directory
$ ( ulimit -c 512 ; ./core.x )
rlim_cur,rlim_max = 524288,524288
malloced 1048576 bytes my pid is 26891
$ ls core.*
core.26891

--
Matthew
When on POSIX, do as POSIX mandates.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]