-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fuzzing test succeeds even though the compiler crashes #6403
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
The test framework is doing the correct. That stack trace is caught, printed and an error is emitted https://github.com/lampepfl/dotty/blob/master/compiler/src/dotty/tools/backend/jvm/GenBCode.scala#L184. Hence the compiler does not actually crash. |
OK we shouldn't catch the exception then, that's not a proper way to report any kind of error. |
Emitting an error when the backend crashes hides the crash from the reporter and fails which cannot be identified by the testing framework.
Agreed. I already opened #6408 with this fix. |
This makes me very very happy. @nicolasstucki I used to modify the compiler as described in the #5006 (comment) I believe there might still be other places where exceptions are ignored. |
Emitting an error when the backend crashes hides the crash from the reporter and fails which cannot be identified by the testing framework.
@alexknvl thanks for the link to your diff. I would have missed someone of those crashes. |
Fix #6403: Do not intercept crashes
Emitting an error when the backend crashes hides the crash from the reporter and fails which cannot be identified by the testing framework.
The text was updated successfully, but these errors were encountered: