#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:           |  
-----------------------+----------------------------------------------------
Description changed by drkirkby:

Old description:

> Reported by John Palmieri on [http://groups.google.com/group/sage-
> release/browse_thread/thread/cc0b1929f66e0658/8c77081af31fc7ef#8c77081af31fc7ef
> sage-release]:
> {{{
> t2.math: seems to build successfully, but I get the following when I
> try to start sage:
>
> ------------------------------------------------------------
> Unhandled SIGSEGV: A segmentation fault occurred in Sage.
> This probably occurred because a *compiled* component
> of Sage has a bug in it (typically accessing invalid memory)
> or is not properly wrapped with _sig_on, _sig_off.
> You might want to run Sage under gdb with 'sage -gdb' to debug this.
> Sage will now terminate (sorry).
> ------------------------------------------------------------
>
> I haven't tried to debug this.  I don't know how to use gdb, in any
> case.  Any suggestions about what the problem might be?  You can find
> the build in /scratch/palmieri/.
> }}}

New description:

 Reported by John Palmieri on [http://groups.google.com/group/sage-
 release/browse_thread/thread/cc0b1929f66e0658/8c77081af31fc7ef#8c77081af31fc7ef
 sage-release]:
 {{{
 t2.math: seems to build successfully, but I get the following when I
 try to start sage:

 ------------------------------------------------------------
 Unhandled SIGSEGV: A segmentation fault occurred in Sage.
 This probably occurred because a *compiled* component
 of Sage has a bug in it (typically accessing invalid memory)
 or is not properly wrapped with _sig_on, _sig_off.
 You might want to run Sage under gdb with 'sage -gdb' to debug this.
 Sage will now terminate (sorry).
 ------------------------------------------------------------

 I haven't tried to debug this.  I don't know how to use gdb, in any
 case.  Any suggestions about what the problem might be?  You can find
 the build in /scratch/palmieri/.
 }}}
 == Hardware and software configuration of t2.math.washington.edu ==
  * [http://www.oracle.com/us/products/servers-storage/servers/sparc-
 enterprise/t-series/031584.htm Sun SPARC Enterprise T5240 Server]
  * 2 x 1167 MHz [http://www.oracle.com/us/products/servers-
 storage/microelectronics/031459.htm UltraSPARC T2 PLUS] processors. (16
 cores and 128 hardware threads in total).
  * 32 GB RAM
  * No swap devices configured.
  * Solaris 10 update 7 (5/09)
  * gcc 4.4.1 configured to use the Sun linker and Sun assembler.
  * Sage was built in on a local ZFS file system (/scratch) as a 32-bit
 application.

--

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