#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:15 SimonKing]:
> But this was all using gcc -- Could it be that t2/Sun compiler behave
differently in that regard?
The compiler used to build Sage on t2.math.washington.edu is gcc. The Sun
compilers are much stricter than gcc, and will not loads of Sage. So this
code is presenting a problem with gcc.
If I build Sage 64-bit on Solaris SPARC it dumps core very easily. I've
noticed the errors often seem to be singular related. Also, if I load a
library for debugging, by the time we have got to the
{{{
sage:
}}}
prompt, there is already a couple of memory leaks. But those should not
cause a crash, unless they exhaust too much memory, which I don't think
they will do. But it does make me a bit suspicious of the Singular/Sage
combination.
One thing worth doing is looking at compiler warnings. There are tons of
them in Sage, but perhaps one near this problem might give us a clue.
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9583#comment:18>
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.
