-
-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Win64 failing unittests #758
Comments
Good idea. Current state for those interested:
Kai's latest EH fixes have reduced the number further. |
Added #761. |
The number is now down to 41: ldc-developers/druntime#14 (comment) |
Update:
|
I'll go ahead with VS 2015 CTP 6 ;) - not too bad, 58 failures:
with ldc-developers/phobos#6 and ldc-developers/druntime#17 (don't forget to uncomment A new common issue seems to have arised (assertion in CRT) which probably accounts for most differences compared to MSVCRT 12. /edit: I think I've fixed that issue, feof() didn't work as stdio.h has changed more than anticipated. I've silently updated the druntime PR and am currently rebuilding the tests. |
Now down to 39 failures with #856 and MSVCRT 14 by simply disabling a printf() call in test_runner.d after a successful unit-test run, the printf() call inside the try-block. Apparently there's some serious corruption going on as otherwise I get a MSVCRT assertion failure
in isatty() called by printf() which probably checks that stdout points to a valid handle.
with excobj being null. The call stack is full of _d_eh_personality() frames. Failing tests:
/edit: If I abort() right before _d_eh_personality:364 if excobj is null, all of above's SEGFAULTs except for core.thread are converted to aborts. I.e., this is crucial. printf() is not usable at that point, causing the same CRT assertion. |
Only remaining failing unittest nowadays is core.thread, which fails in release in line https://github.com/ldc-developers/druntime/blob/ldc/src/core/thread.d#L5467, a Win64-specific test. |
The status is still the same. #1103 points to the single remaining 'issue' incl. details, so I'm going to close this. |
Let's collect information about the failing unittests.
_d_arraycatnT
contains varargs and crashes. Responsible for rt.lifetime, core.time, std.array, std.conv,... probably most of them.Potentially related to Vararg functions does not compile on x86_64 #702 core.stdc.stdarg doesn't work on 64 bits #73 Crash when compiling dbox (also compiling forever on release) #699
The text was updated successfully, but these errors were encountered: