[Top][All Lists]

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

Re: [Chicken-hackers] Issue installing sxpath

From: Thomas Hintz
Subject: Re: [Chicken-hackers] Issue installing sxpath
Date: Sun, 28 Apr 2013 20:49:01 -0700

On Sun, Apr 28, 2013 at 3:17 PM, Thomas Hintz <address@hidden> wrote:
> On Sun, Apr 28, 2013 at 1:40 PM, Felix
> <address@hidden> wrote:
>> From: Thomas Hintz <address@hidden>
>> Subject: [Chicken-hackers] Issue installing sxpath
>> Date: Sun, 28 Apr 2013 09:57:55 -0700
>>> I'm unable to install sxpath. I haven't run across any other issues
>>> installing other eggs.
>>> Any help in figuring out what the issue is or pointing me in the right
>>> direction would be appreciated.
>>> chicken-install sxpath
>>> retrieving ...
>>> connecting to host "", port 80 ...
>>> requesting "/henrietta.cgi?name=sxpath&mode=default" ...
>>> reading response ...
>>> HTTP/1.1 200 OK
>>> Date: Sun, 28 Apr 2013 16:51:55 GMT
>>> Server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/0.9.9-dev DAV/2
>>> SVN/1.7.8 PHP/5.4.13 mod_fastcgi/2.4.6
>>> Connection: close
>>> Transfer-Encoding: chunked
>>> Content-Type: text/plain
>>> reading chunks ...[panic] out of memory - heap full while resizing -
>>> execution terminated
>> This looks like a corrupt heap. The egg is quite large - perhaps the download
>> triggers some corner case in the networking- or I/O system. I assume
>> "chicken-install -r sxpath" fails as well? Is this crash always reproducible?
> Thanks felix. chicken-install -r sxpath succeeds. chicken-install
> sxpath always fails.

Sorry guys, I was mostly wrong. chicken-install -r sxpath worked
exactly once. I had some more time to play with it and I ran
chicken-install sxpath and chicken-install -r sxpath about 20 times
each and both of them failed 100% of the time.

I honestly don't much about the low level workings of chicken but I
would be glad to help look into it given some pointers. I could also
setup a freebsd jail on the system for someone to play with if that
would be easier.

Thomas Hintz

reply via email to

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