Summary
Running MinGW-produced Chicken from a MSVC-produced executable causes a stack overflow during initialization
Metadata
- Id: 42ee9c7c31d48bd7453456956165d8348ee256e8
- Trac id: 1453
- Type: defect
- Reporter: jrobbins
- Owner:
- Cc:
- Status: new
- Component: unknown
- Estimated difficulty:
- Resolution:
- Priority: major
- Milestone: someday
- Version: 4.13.0
- Changetime: 2018-04-23 15:32:31 UTC
- Created: 2018-04-18 17:43:14 UTC
- Keywords:
Attachments
- 42ee9c7c31d48bd7453456956165d8348ee256e8/attachments/chicken-crash.tar.gz
- 42ee9c7c31d48bd7453456956165d8348ee256e8/attachments/patch.txt
Description
I am on Windows. I have a program, compiled via MSVC, that has a dependency on libchicken.dll, compiled via MinGW, both 64 bit. It successfully calls CHICKEN_run with the default toplevel, but during the loading of the modules, the program segfaults with a stack overflow error in various places, usually around the time it hits loading modules.scm.
It seems that Chicken underestimates the size of the stack when ran in this manner, causing it to run out of stack space much sooner than it anticipates, causing the segfault when it fails to resize the stack.
Attached is a set of files that can replicate the issue. Running make should produce call_from_cl.exe, which will segfault when run. The libchicken.dll it needs should be produced via the mingw-msys platform. You'll need MSVC's cl.exe and lib.exe installed to compile.
Changes and comments
[2018-04-18 17:48:23 UTC] jrobbins attached chicken-crash.tar.gz (description=#f)
[2018-04-23 15:32:31 UTC] jrobbins wrote:
I have found a solution to the issue- It seems like setjmp/longjmp are known to be buggy in MinGW64. Attached is a patch that solves these issues.