On Feb 4, 2013, at 2:28 PM, Felix wrote:
>
> Perhaps, but I really don't see a problem of allowing a limit
> on heap allocation in the runtime system.
I think a segfault is an appropriate response to OOM, but I wonder
if it's possible to panic() instead if the heap size can't be increased
as nee
From: Peter Bex
Subject: Re: [Chicken-users] Segfault with large data-structures (bug)
Date: Mon, 4 Feb 2013 00:16:47 +0100
> On Mon, Feb 04, 2013 at 12:10:16AM +0100, Felix wrote:
>> > But why not just use ulimit? It can be set per process, so I don't see
>> > the need to have a second ulimit-l
I am running the following test on Red Hat Enterprise Linux Server
release 6.3 (Santiago):
$ uname -m
x86_64
$ getconf LONG_BIT
64
$ cat crash.scm
#! /usr/xxx/bin/csi -s
(use syslog)
(openlog #f opt/pid facility/local0)
$ csi crash.scm
CHICKEN
(c)2008-2011 The Chicken Team
(c)2000-2007 Felix L
cleaning up my backlog, sorry for the late reply
On Jan 31 2013, Felix wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/29/2013 08:16 PM, Felix wrote:
I'm turning to you because I have no idea how to continue with
analyzing a very odd behavior of my channel egg's test cases.
Basica
Hi Agrest,
* Agrest [130204 00:32]:
> Hello!
>
> I've found the bug in the SDL egg.
>
> If the egg is installed via ``chicken-install``, any program segfaults
> on (ttf-init). However, it works when the SDL egg is installed using
> the Makefile supplied.
>
> My system is Ubuntu 12.04.
>
> I'
