Memory corruption bug with Jvm::attachLibrary
Matthewacon opened this issue · comments
Matthewacon commented
There seems to be a memory corruption bug with Jvm::attachLibrary
that is causing intermittent and random issues with other parts of fake-jni
. This may have been introduced over 100 commits ago, when attaching the current binary stopped working for the main fake-jni
example.
The latest build of baron
exhibits this bug. The current build should simply print the stacktrace and exit, however, after running it several times it may do any number of things, including reprint the stacktrace several times.