#10018: Unhandled SIGSEGV after bnfcertify()
------------------------+---------------------------------------------------
Reporter: jdemeyer | Owner: jdemeyer
Type: defect | Status: new
Priority: critical | Milestone: sage-4.6
Component: c_lib | Keywords: segfault segmentation fault allocatemem
interrupt _sig_on _sig_retry
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by jdemeyer):
Replying to [comment:13 leif]:
> The actual error message should be {{{vsnprintf()}}}'ed into a buffer
(upstream) such that we can also propagate the real cause.
That is more or less the idea of #9640.
But I also noticed that the whole exception-catching mechanism can be
vastly improved (for example, now there is a general signal-handling
facility in Sage and a specific error-handling facility for PARI which
should be merged into one system). Also, there is essentially no testing
code for this Cython error handling. Good testing code should have caught
#10018. All this should eventually be in #9678.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10018#comment:14>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
