I'm suddenly getting segfaults when running tests on Windows. It works fine on Linux. I reduced it to a few lines (plus a dependency) with dustmite, but they don't really make sense[1]. Nevertheless they do trigger the segfault.

Can someone with Windows 10 and dmd 2.087.0 try the following and see if it crashes please?

git clone https://github.com/zorael/tests -b wintestcrash && cd tests && dub test

If it ends with an assertion failure, okay, darn. If it "exited with code -1073741819" I'll have confirmed it happens for more than just me and AppVeyor, and thus can go ahead and file a bug report.

Running custom 'unittest' configuration.
Performing "unittest" build using C:\D\dmd2\windows\bin\dmd.exe for x86_64. cachetools 0.1.2: target for configuration "library" is up to date.
requests 1.0.9: target for configuration "std" is up to date.
test ~wintestcrash: building configuration "unittest"...
Linking...
To force a rebuild of up-to-date targets, run again with --force.
Running .\test.exe
Program exited with code -1073741819

[1]: https://github.com/zorael/tests/blob/wintestcrash/source/app.dx

Reply via email to