Skip to content
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

Misleading segfault message #172

Open
culler opened this issue Jun 5, 2023 · 0 comments
Open

Misleading segfault message #172

culler opened this issue Jun 5, 2023 · 0 comments

Comments

@culler
Copy link

culler commented Jun 5, 2023

Many SageMath users, including me, have seen the following message hundreds of times:

Unhandled SIGSEGV: A segmentation fault occurred.
This probably occurred because a compiled module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.

Not once have I encountered a case where the segfault was actually caused by not properly wrapping some code in sig_on and sig_off. Every segfault produces this message. So the message is not only incorrect and useless, it is also misleading. Why not get rid of it, or replace it by something useful, such as a link to an issues page?

This issue was also reported as SageMath #35706. At the suggestion of Dave Witte-Morris I am duplicating it here, since the message is actually generated by cysignals.

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

No branches or pull requests

1 participant