On Mon 04 Apr 2011 04:01, Leo writes:
> cc1(57938) malloc: *** error for object 0x10357a148: incorrect checksum for
> freed object - object was probably modified after being freed.
> *** set a breakpoint in malloc_error_break to debug
> vm-engine.c: In function 'vm_regular_engine':
> vm-engine.c
On 2011-04-04 15:13 +0800, Andy Wingo wrote:
>> cc1(57938) malloc: *** error for object 0x10357a148: incorrect checksum for
>> freed object - object was probably modified after being freed.
>> *** set a breakpoint in malloc_error_break to debug
>> vm-engine.c: In function 'vm_regular_engine':
>> v
Hi,
co-routine linkage problem solved!
All it takes, is taking care that each [full] continuation
seen by one co-routine are equivalent, so it doesn't matter
which one gets saved and restored. No continuation-barrier
or dynamic-wind required!
While not obvious at first glance, doing so is easy e
On Mon 04 Apr 2011 10:00, Leo writes:
> On 2011-04-04 15:13 +0800, Andy Wingo wrote:
>>> cc1(57938) malloc: *** error for object 0x10357a148: incorrect checksum for
>>> freed object - object was probably modified after being freed.
>>> *** set a breakpoint in malloc_error_break to debug
>>> vm-e
On Sun 03 Apr 2011 23:23, John Proctor writes:
> However, if I take a scheme source file such as foo.ss with nothing more than
> a single express e.g. (+ 1 1) and try :
>
> $ nc localhost 9000 < foo.ss
>
> the guile instance dies immediately with no errors or anything.
Can anyone reproduce this
On 2011-04-05 04:44 +0800, Andy Wingo wrote:
> Sorry, didn't mean to sound hostile there. I don't know anything about
> Mac OS 10.6. However if it is still the case that they ship something
> called gcc and something called gcc-4.2, you can compile with
> ./configure ... CC=gcc-4.2, and you probabl
