Ask Your Question

After upgrade to 6.9 we obtain SIGILL ...

asked 2015-10-19 11:32:29 +0200

GGuasp gravatar image

updated 2015-10-22 21:43:56 +0200

FrédéricC gravatar image

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.

edit retag flag offensive close merge delete


In what sense did you upgrade? Did you download a new binary? If so, which one? What version of Mac OS do you have? Thanks!

kcrisman gravatar imagekcrisman ( 2015-10-19 14:49:28 +0200 )edit

I 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 .

GGuasp gravatar imageGGuasp ( 2015-10-20 09:40:51 +0200 )edit

Hmm, perhaps this is similar to

kcrisman gravatar imagekcrisman ( 2015-10-20 16:39:08 +0200 )edit

And - but indeed the Core 2 Duo has had some problems with this in the past.

kcrisman gravatar imagekcrisman ( 2015-10-20 16:40:58 +0200 )edit

To 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)


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.

slelievre gravatar imageslelievre ( 2018-02-17 01:58:52 +0200 )edit

2 Answers

Sort by » oldest newest most voted

answered 2015-11-02 16:56:53 +0200

this post is marked as community wiki

This post is a wiki. Anyone with karma >750 is welcome to improve it.

Same problem on Mac Pro 2010 with X5690 processors.

edit flag offensive delete link more


Running sage with -gdb reveals the illegal instruction is in libmpir in function __gmpf_set_d.

ljbo gravatar imageljbo ( 2015-11-02 17:56:32 +0200 )edit

It is a macro actually: the function is mpf_set_d.

ljbo gravatar imageljbo ( 2015-11-02 17:57:29 +0200 )edit

So anyway, my processors are the latest Nehalem. I guess the illegal instruction came with Sandy Bridge or Ivy Bridge.

ljbo gravatar imageljbo ( 2015-11-02 18:00:09 +0200 )edit

Wow, that is pretty specific! Hopefully it will help... my guess is still a simple incompatibility though.

kcrisman gravatar imagekcrisman ( 2015-11-03 14:57:17 +0200 )edit

I 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.)

Dima gravatar imageDima ( 2015-11-03 15:56:21 +0200 )edit

answered 2015-10-20 16:43:15 +0200

kcrisman gravatar image

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.)

edit flag offensive delete link more


sage-6.6-x86_64-Darwin-OSX_10.7_x86_64-app fails (also)

Something is broken in my system?

GGuasp gravatar imageGGuasp ( 2015-10-21 10:16:10 +0200 )edit

No, 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.

kcrisman gravatar imagekcrisman ( 2015-10-21 14:15:51 +0200 )edit

After 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

GGuasp gravatar imageGGuasp ( 2015-10-22 09:29:32 +0200 )edit

You may not be done compiling, though. This is a good discussion for sage-devel.

kcrisman gravatar imagekcrisman ( 2015-10-22 16:42:08 +0200 )edit

Correct, the compilation has no finished. But I have obtained a working Sage (notebook included).

GGuasp gravatar imageGGuasp ( 2015-10-23 09:03:27 +0200 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2015-10-19 11:32:29 +0200

Seen: 840 times

Last updated: Nov 02 '15