fix failing SIGSEGV spec #6995
Merged
fix failing SIGSEGV spec #6995
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
|
I've noticed that failing spec as well. Thanks for investigating! |
jhass
approved these changes
Oct 26, 2018
RX14
approved these changes
Oct 26, 2018
|
Probably lack of ASLR (boo) |
RX14
added
kind:bug
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.
On linux the spec "seg fault reports SIGSEGV" is intermittently failing because the process is exiting with success. I.e, it looks like the desired seg fault is not being generated. I have not reproduced this, but presumably the hard-coded pointer address in the spec is intermittently in user space.
Fixed by dereferencing a null pointer instead, which should always generate a seg fault.