ASKSAGE: Sage Q&A Forum - RSS feedhttps://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Sat, 09 Jun 2012 22:05:40 +0200Should evaluating 1.0e-15 produce an Unhandled SIGILLhttps://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/Since downloading Sage 5.0 evaluating 1.0e-15 produces an Unhandled SIGILL in the notebook on Mac OSX. Has the input format changed from what it was in 4.7?
Now it seems I have to type 1.0*10.0^-15 (a lot more characters!)
...or is this a bug?
sage: 10.0^-1
0.100000000000000
sage: 1.0e-1
------------------------------------------------------------------------
Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a *compiled* component of Sage has a bug
in it and 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.
------------------------------------------------------------------------Sat, 09 Jun 2012 12:40:06 +0200https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/Answer by calc314 for <p>Since downloading Sage 5.0 evaluating 1.0e-15 produces an Unhandled SIGILL in the notebook on Mac OSX. Has the input format changed from what it was in 4.7?</p>
<p>Now it seems I have to type 1.0*10.0^-15 (a lot more characters!)</p>
<p>...or is this a bug?</p>
<pre><code>sage: 10.0^-1
0.100000000000000
sage: 1.0e-1
------------------------------------------------------------------------
Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a *compiled* component of Sage has a bug
in it and 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.
------------------------------------------------------------------------
</code></pre>
https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?answer=13680#post-id-13680If you have a duo core slightly older Mac, then I think this is the same issue that I was having at: [Sage 5.0 plot issue](http://ask.sagemath.org/question/1424/sage-50-plot-issue).
You might want to read @kcrisman's answer there. He suggested trying the following command to see if it would crash:
sage: int(2.4)
There is also a ticket on this at: [Trac 12954](http://trac.sagemath.org/sage_trac/ticket/12954)
Apparently, building Sage from scratch on the system will resolve this issue, but I have not tried that yet.
Sat, 09 Jun 2012 15:24:35 +0200https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?answer=13680#post-id-13680Comment by martinB for <p>If you have a duo core slightly older Mac, then I think this is the same issue that I was having at: <a href="http://ask.sagemath.org/question/1424/sage-50-plot-issue">Sage 5.0 plot issue</a>.</p>
<p>You might want to read <a href="/users/41/kcrisman/">@kcrisman</a>'s answer there. He suggested trying the following command to see if it would crash:</p>
<pre><code>sage: int(2.4)
</code></pre>
<p>There is also a ticket on this at: <a href="http://trac.sagemath.org/sage_trac/ticket/12954">Trac 12954</a></p>
<p>Apparently, building Sage from scratch on the system will resolve this issue, but I have not tried that yet.</p>
https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?comment=19636#post-id-19636oh well... I guess I better figure out how to build this thing then.Sat, 09 Jun 2012 15:42:01 +0200https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?comment=19636#post-id-19636Comment by kcrisman for <p>If you have a duo core slightly older Mac, then I think this is the same issue that I was having at: <a href="http://ask.sagemath.org/question/1424/sage-50-plot-issue">Sage 5.0 plot issue</a>.</p>
<p>You might want to read <a href="/users/41/kcrisman/">@kcrisman</a>'s answer there. He suggested trying the following command to see if it would crash:</p>
<pre><code>sage: int(2.4)
</code></pre>
<p>There is also a ticket on this at: <a href="http://trac.sagemath.org/sage_trac/ticket/12954">Trac 12954</a></p>
<p>Apparently, building Sage from scratch on the system will resolve this issue, but I have not tried that yet.</p>
https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?comment=19633#post-id-19633Not at all! Look in http://sage.math.washington.edu/home/buildbot/binaries/sage/5.0.1.rc1/ and see if your architecture lives there. I have a feeling that this will be VERY similar to the released 5.0.1, which largely exists to have a release fixing this bug.Sat, 09 Jun 2012 22:05:40 +0200https://ask.sagemath.org/question/9053/should-evaluating-10e-15-produce-an-unhandled-sigill/?comment=19633#post-id-19633