[racket-dev] error with futures and the compiler

Are the unsafe operations ever misapplied?

Robby

On Tue, Sep 20, 2011 at 4:27 PM, Sam Tobin-Hochstadt <samth at ccs.neu.edu> wrote:
> The attached program works fine, and if compiled, it works fine with
> small inputs:
>
> [samth at punge] r tst.rkt 40 > /dev/null
> [samth at punge] r tst.rkt 4000 > /dev/null
> [samth at punge] raco make tst.rkt
> [samth at punge] r tst.rkt 40 > /dev/null
>
> But with big inputs, when compiled, it fails:
>
> [samth at punge] r tst.rkt 4000 > /dev/null
> compiled/tst_rkt.zo::6943: read (compiled): ill-formed code
> [../../../racket/gc2/../src/read.c:4751]
>
>  === context ===
> raise called (with non-exception value) by exception handler: #f;
> original exception raised: compiled/tst_rkt.zo::6943: read (compiled):
> ill-formed code [../../../racket/gc2/../src/read.c:4751]
> internal error: failure during atomic
> Aborted
> --
> sam th
> samth at ccs.neu.edu
>
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/dev
>