Closed Lovesan closed 5 years ago
Here's a bounty of $1000 https://www.bountysource.com/issues/75904410-sbcl-crashes-while-net-is-here
It seems that you can disable signal munging by not passing PAL_INITIALIZE_REGISTER_SIGNALS to https://github.com/dotnet/coreclr/blob/86e600cef40a650a8ffb294dd195186b1679609b/src/pal/src/init/pal.cpp#L302 which is passed by deafault https://github.com/dotnet/coreclr/blob/835836c9d34409af0f31529201dfd57cb2bd053c/src/pal/inc/pal.h#L356
but who knows what that's going to do to their runtime.
Here's the code that could be used for reproducing the issue, without the need to load this library: https://gist.github.com/Lovesan/d8c184c8a2d286255af03852e3019bb2
Bug description at launchpad: https://bugs.launchpad.net/sbcl/+bug/1834964
@stassats Implemented a workaround in SBCL which i have incorporated into version 0.3.0
@stassats please press 'Claim bounty' button on bountysource
SBCL implementation crashes randomly on Linux should you load .Net Core runtime into a process.
This has something to do with unix signals, most likely, because the usual displayed error is the following:
The resolution, though hardly defined, is, as you might except, would be, as you would guess - the execution of the tests, with no error, and no crashes, using 'sbcl --script tests.lisp'.