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.
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.