It varies a lot: When running the Scala example from the SBT shell it is maybe 
1 out of 5. For the Java example on the debug branch I'm using the `run.sh` 
which simply performs 1000 iterations and terminates on a crash. I'm usually 
crashing within <200 iterations, sometimes in the first 10, max was maybe 400.

When replacing the .so by the plain C library I'm reaching 1000 iterations 
without a crash. But I'm still not sure if it may be a JVM bug, which is only 
triggered by something in the Nim implementation because:

  * The traceback always points to `VM_Version::get_processor_features()` \-- 
with true stack corruption you would expect more random tracebacks, right?
  * When running a longer computation on Nim side, the crash always seems to 
happen after the function has returned.


Reply via email to