test-signalhandler: test SIGFPE / assert exitcodes #7238
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
firewave
force-pushed
the
sigfpe
branch
2 times, most recently
from
5d21f93 to
ef72a3c
Compare
danmar
approved these changes
Jan 23, 2025
| return 2; | ||
| if (std::feraiseexcept(FE_ALL_EXCEPT) != 0) | ||
| return 3; | ||
| return 1 % -1; |
There was a problem hiding this comment.
I imagine that 1 % -1 is always 0, isn't it? why not write 0 here? Because it's testcode?
There was a problem hiding this comment.
That is the invalid floating-point operation which is causing the exception. The code above is just telling it to raise the exception and to trap it (cause the signal).
https://www.gnu.org/software/libc/manual/html_node/FP-Exceptions.html
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.