-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Assertion failure causes wrong exit status #4547
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
Comments
I don't know of the implications, but removing the |
Previous pull request with discussion of solutions #5054 |
Not critical for 0.6; removing milestone |
I'm happy to say that with Otherwise it'd just stay open until then because it doesn't look like it's going to be fixed in the meantime. |
Reopening, this should have a test. |
Closed in #7923 |
Causes the program to return with exit status 0. Thankfully removing
os::args()
makes it return with nonzero, but it appears that at any point after the invocation ofos::args()
an assertion failure will cause an exit status of 0.I ran this against a compiler built at e51ec26
The text was updated successfully, but these errors were encountered: