[MLton] Crashes with 64-bit native code generator on Windows
matthew.fluet at gmail.com
Mon Nov 30 08:59:07 PST 2009
On Mon, Nov 23, 2009 at 8:39 PM, David Hansel
<hansel at reactive-systems.com>wrote:
> I was looking into what could be causing the problem and came across
> file MLton/lib/mlton/sml/mlnlffi-lib/memory/linkage-libdl.sml which
> is of course used by the FFI. I wasn't completely sure what the "era"
> deal in that code is, so I changed the body of function "get" to just
> "f()", resolving the FFI function's address before every call.
The "era" is supposed to invalidated dynamically loaded library addresses if
the executable is started up again after saving the world
(MLton.World.save). Because it is a new executable invocation, the
dynamically linked library needs to be reloaded and it might end up at a
different address. This isn't actually done in the linkage-libdl.sml code;
see the commented out "Cleaner.addNew" application. I don't recall why it
is disabled. In any case, unless you are saving and loading worlds, it
shouldn't affect your code.
> that change, all crashes were gone. Furthermore, changing the body
> of "get" to just "a" does NOT fix the crashes. That looked good
> so I added some "print" statements in "get" to see whether there is
> a problem with the address not being resolved properly. Unfortunately,
> just adding the "print" statements also made the crashes go away. In
> fact, just adding 'print "";' at the beginning of "get" eliminates
> the crashes. Interestingly, this eliminates the crashes completely.
> With other changes in our code I was able to eliminate some instances
> of the crashes but new ones would pop up at other places. I suspect
> that the proximity of this code to the actual FFI calls might play
> a role in that.
This, and your next email, suggest that it is a bug with the native
codegen. The probable role that the proximity of the "print" call plays is
that there will be an C function call invoked by the "print", which "resets"
the register allocator. Without the "print" call, there is a wider scope
over which the register allocator is able to work, and, apparently, is
mistakenly dropping a def.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MLton