Skip to content

Give an explicit message when SIGSEGV happens. #3712

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

Merged
merged 1 commit into from
Aug 25, 2016

Conversation

ezyang
Copy link
Contributor

@ezyang ezyang commented Aug 22, 2016

Fixes #767.

Signed-off-by: Edward Z. Yang [email protected]

@mention-bot
Copy link

@ezyang, thanks for your PR! By analyzing the annotation information on this pull request, we identified @dcoutts and @BardurArantsson to be potential reviewers

@23Skidoo
Copy link
Member

LGTM.

@erikd
Copy link
Member

erikd commented Aug 22, 2016

👍

@ezyang
Copy link
Contributor Author

ezyang commented Aug 22, 2016

Unfortunately, the patch doesn't work. Investigating.

@ezyang
Copy link
Contributor Author

ezyang commented Aug 22, 2016

OK, found the bug.

@ezyang ezyang force-pushed the pr/setup-segfault-msg branch from 44b57e5 to 64b6ec0 Compare August 22, 2016 23:13
@ezyang
Copy link
Contributor Author

ezyang commented Aug 23, 2016

Heh, the Windows version of the test case explodes in an... interesting way. Let me see if I can tweak it.

@ezyang ezyang force-pushed the pr/setup-segfault-msg branch 2 times, most recently from b600a2b to 4e3fc54 Compare August 24, 2016 06:21
@ezyang ezyang force-pushed the pr/setup-segfault-msg branch from 4e3fc54 to b45df92 Compare August 24, 2016 07:42
@ezyang ezyang merged commit c4fc3bd into haskell:master Aug 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants