[Openmcl-devel] crash without report
Hans Hübner
hans at huebner.org
Mon Nov 10 11:12:16 PST 2008
On Mon, Nov 10, 2008 at 20:04, Alexander Repenning
<ralex at cs.colorado.edu> wrote:
> this may have been discussed in some other context but I cannot find any
> trace. Anyway, while usually pretty stable CCL 1.2 (mac) works well with
> Cocoa in general and even reports, without crashing on some memory
> management issues. But once in a while CCL really does crash but
> unfortunately without creating a crashlog file. What is missing? I have
> COREDUMPS=-YES-
> in etc/hostconfig
> but when getting a Nov 10 11:54:15 Ristretto-to-Go-7 com.apple.launchd[67]
> ([0x0-0x15015].com.clozure.Clozure CL[119]): Exited: Killed
> there is no crash.log
To me, this looks as if the operating system has killed the CCL
process, presumably because of a swap space shortage. Check your
'messages' file (presumably /var/log/messages, but could be somewhere
else on Mac OS X) for "out of swap space" messages?
-Hans
More information about the Openmcl-devel
mailing list