-
Notifications
You must be signed in to change notification settings - Fork 5
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
v1.0.0 cause Program exited with code -11 (v0.13.3 is fine) #99
Comments
Would it be possible to share the test/project that triggers this error? also, the compiler version would also be helpful to know. |
Actually I think I found the problem: In one of my own sharedStaticCtor, some function called Maybe in this case, all such Assert should be just ignored. (I will try to remove such Assert, and see what happens). |
yes, to improve the integration with the Trial test runner, I had to introduce some global states. It's better not to have asserts in a module constructor. I'm currently working on a better solution to it, but I don't have enough time... |
It is confirmed that this is the cause of the problem (I remove such Assert calls in the sharedStaticCtor call path, it works now).
As I suggested: for now, maybe just issue a warning message, and ignore such assert? (it should be detectable: just check a flag that fluent-asserts is not fully init-ed). |
Hit by this issue again. Any update? Another thought: make Assert only do real call in version (unittest), otherwise, just NO-OP. |
I only had a little time for this library. I want to spend some time on Friday on this. I hope I can fix all open issues then. Otherwise, PRs are always welcomed. |
maybe the problems caused by some sharedStaticCtor ?
The text was updated successfully, but these errors were encountered: