ASKSAGE: Sage Q&A Forum - Individual question feedhttps://ask.sagemath.org/questions/Q&A Forum for SageenCopyright Sage, 2010. Some rights reserved under creative commons license.Fri, 16 Feb 2018 18:59:55 -0600After upgrade to 6.9 we obtain SIGILL ...https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/After upgrding to 6.9 version I obtain
------------------------------------------------------------------------
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().
Sage will now terminate.
------------------------------------------------------------------------
as response to use of float 1.2 but 12/10. works fine.
iMac (2008) Intel Core 2 Duo.Mon, 19 Oct 2015 04:32:29 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/Comment by slelievre for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=41159#post-id-41159To display inline code, like `z = x*y`, use backticks.
To display blocks of code or error messages, skip a line above and below,
and do one of the following (all give the same result):
- indent all code lines with 4 spaces
- select all code lines and click the "code" button (the icon with '101 010')
- select all code lines and hit ctrl-K
For instance, typing
If we define `f` by
def f(x, y):
return (x, y)
then `f(2, 3)` returns `(2, 3)` but `f(2)` gives:
TypeError: f() takes exactly 2 arguments (1 given)
produces:
> If we define `f` by
>
> def f(x, y):
> return (x, y)
>
> then `f(2, 3)` returns `(2, 3)` but `f(2)` gives:
>
> TypeError: f() takes exactly 2 arguments (1 given)
Please edit your question to do that.Fri, 16 Feb 2018 18:58:52 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=41159#post-id-41159Comment by kcrisman for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30145#post-id-30145And http://ask.sagemath.org/question/7907/float-numbers-error/ - but indeed the Core 2 Duo has had some problems with this in the past.Tue, 20 Oct 2015 09:40:58 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30145#post-id-30145Comment by kcrisman for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30144#post-id-30144Hmm, perhaps this is similar to http://ask.sagemath.org/question/26640/unhandled-sigill-by-using-floats-such-as-11/Tue, 20 Oct 2015 09:39:08 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30144#post-id-30144Comment by GGuasp for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30135#post-id-30135I dowloaded the new binary (sage-6.9-x86_64-Darwin-OSX_10.10_x86_64-app.dmg 2015-10-14).
Using MacOS 10.10.5 (Yosemite).
In fact, I think the problem appears yet in 6.8 .Tue, 20 Oct 2015 02:40:51 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30135#post-id-30135Comment by kcrisman for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30119#post-id-30119In what sense did you upgrade? Did you download a new binary? If so, which one? What version of Mac OS do you have? Thanks!Mon, 19 Oct 2015 07:49:28 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30119#post-id-30119Answer by ljbo for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?answer=30404#post-id-30404Same problem on Mac Pro 2010 with X5690 processors.Mon, 02 Nov 2015 09:56:53 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?answer=30404#post-id-30404Comment by Dima for <p>Same problem on Mac Pro 2010 with X5690 processors.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30430#post-id-30430I take this as you have an upgraded Mac, right? And which version of OSX? (IMHO it's a non-standard config anyway, and you'd be best off building from source.)Tue, 03 Nov 2015 08:56:21 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30430#post-id-30430Comment by kcrisman for <p>Same problem on Mac Pro 2010 with X5690 processors.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30426#post-id-30426Wow, that is pretty specific! Hopefully it will help... my guess is still a simple incompatibility though.Tue, 03 Nov 2015 07:57:17 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30426#post-id-30426Comment by ljbo for <p>Same problem on Mac Pro 2010 with X5690 processors.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30407#post-id-30407So anyway, my processors are the latest Nehalem. I guess the illegal instruction came with Sandy Bridge or Ivy Bridge.Mon, 02 Nov 2015 11:00:09 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30407#post-id-30407Comment by ljbo for <p>Same problem on Mac Pro 2010 with X5690 processors.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30406#post-id-30406It is a macro actually: the function is mpf_set_d.Mon, 02 Nov 2015 10:57:29 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30406#post-id-30406Comment by ljbo for <p>Same problem on Mac Pro 2010 with X5690 processors.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30405#post-id-30405Running sage with -gdb reveals the illegal instruction is in libmpir in function __gmpf_set_d.Mon, 02 Nov 2015 10:56:32 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30405#post-id-30405Answer by kcrisman for <p>After upgrding to 6.9 version I obtain</p>
<hr/>
<p>Unhandled SIGILL: An illegal instruction occurred in Sage.
This probably occurred because a <em>compiled</em> component of Sage has a bug
in it and is not properly wrapped with sig_on(), sig_off().</p>
<h2>Sage will now terminate.</h2>
<p>as response to use of float 1.2 but 12/10. works fine.</p>
<p>iMac (2008) Intel Core 2 Duo.</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?answer=30146#post-id-30146So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)Tue, 20 Oct 2015 09:43:15 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?answer=30146#post-id-30146Comment by GGuasp for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30175#post-id-30175sage-6.6-x86_64-Darwin-OSX_10.7_x86_64-app
fails (also)
Something is broken in my system?Wed, 21 Oct 2015 03:16:10 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30175#post-id-30175Comment by kcrisman for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30181#post-id-30181No, it just means that the 10.7 one is too old compared to 10.10, and the 10.10 one is built with too new a processor for your machine. So you will probably have to build from scratch. It is not so hard to do this, the main thing is to get the "command line tools" from Apple. Search this site for what that is or ask back :) but unfortunately it's very hard to provide binaries for every system.Wed, 21 Oct 2015 07:15:51 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30181#post-id-30181Comment by kcrisman for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30220#post-id-30220You may not be done compiling, though. This is a good discussion for sage-devel.Thu, 22 Oct 2015 09:42:08 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30220#post-id-30220Comment by GGuasp for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30240#post-id-30240Correct, the compilation has no finished.
But I have obtained a working Sage (notebook included).Fri, 23 Oct 2015 02:03:27 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30240#post-id-30240Comment by kcrisman for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30250#post-id-30250Good! But what I meant was that there may be some other packages inside that also didn't finish.Fri, 23 Oct 2015 12:14:10 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30250#post-id-30250Comment by GGuasp for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30319#post-id-30319I'm testing if appears any "evident" problem (not at this time, but I'm a "basic user").
Any chance to avoid this kind of problem on 6.10?Wed, 28 Oct 2015 10:03:45 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30319#post-id-30319Comment by kcrisman for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30323#post-id-30323I'm not sure. And I have no idea why Sage wouldn't have compiled fine on this platform. I suggest using sage-support@googlegroups.com for that, as this forum isn't really ideal for diagnosing long error messages :( But you could send the R build log file there and see if there was something in it.Wed, 28 Oct 2015 14:38:48 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30323#post-id-30323Comment by GGuasp for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30210#post-id-30210After 6 o 7 h. compilation finishes with error on r-3.2.2.p0 (some part of R?).
Sage itself seems to work OK!!!
The log finnishes with:
make[7]: *** [sysdata] Error 133
make[6]: *** [all] Error 2
make[5]: *** [R] Error 1
make[4]: *** [R] Error 1
make[3]: *** [R] Error 1
Error building R.
real 6m16.079s
user 4m7.538s
sys 0m52.003s
************************************************************************
Error installing package r-3.2.2.p0
************************************************************************Thu, 22 Oct 2015 02:29:32 -0500https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=30210#post-id-30210Comment by slelievre for <p>So my guess is that your processor can't handle some instruction in the binaries, which I think are made with a machine newer than 7 years old. (Which doesn't mean there is anything wrong with your machine, but you may need to compile from scratch, or perhaps try one of the binaries for older OS X versions.)</p>
https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=41160#post-id-41160One suggestion when `make` ends with an error: run `make` again. It might go further at each step.Fri, 16 Feb 2018 18:59:55 -0600https://ask.sagemath.org/question/30117/after-upgrade-to-69-we-obtain-sigill/?comment=41160#post-id-41160