It looks like there's a problem with the ffi implementation of (malloc ... 'raw) in Windows. In particular, if I call 'free()' in a C extension on a block of memory that was allocated with (malloc ... 'raw), I get the Windows equivalent of a core dump, with an exception code that indicates "heap corruption". I have a small piece of code that illustrates this, although one of the steps is compiling a windows DLL, which is somewhat nontrivial (though the source file is only a few lines). Before I submit a bug report, is the Windows (malloc ... 'raw) already known not to cooperate with free()? The obvious workaround is... just not to free the memory, but this is going to be an unsatisfying solution when dealing with 30Meg sound files.
Thanks! John
smime.p7s
Description: S/MIME cryptographic signature
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
