#9583: Unhandled SIGSEGV with 4.5.2.alpha0 on t2
-----------------------+----------------------------------------------------
   Reporter:  mpatel   |       Owner:  drkirkby  
       Type:  defect   |      Status:  new       
   Priority:  blocker  |   Milestone:  sage-4.5.2
  Component:  solaris  |    Keywords:            
     Author:           |    Upstream:  N/A       
   Reviewer:           |      Merged:            
Work_issues:           |  
-----------------------+----------------------------------------------------

Comment(by drkirkby):

 Replying to [comment:8 jhpalmieri]:
 > After replacing {{{libs/singular/option.pyx}}} with the one from
 sage-4.5.rc1 (the version I happen to have lying around), and doing
 {{{sage -b}}}, sage started without segfaulting.  I assume that a bunch of
 doctests will break now since I haven't backed out all of the changes from
 #1396, but this file does seem to be the problem.

 Thank you John. I will try that.

 It would be nice to know if there was a good way to do this in Mercurial
 though. Adding patches is quite easy, but I assume there is a way to back
 them out even after they have been committed.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:9>
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.

Reply via email to