Ask Your Question

Should evaluating 1.0e-15 produce an Unhandled SIGILL

asked 2012-06-09 05:40:06 -0600

martinB gravatar image

updated 2012-06-09 06:22:50 -0600

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
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.
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2012-06-09 08:24:35 -0600

calc314 gravatar image

updated 2012-06-09 08:26:32 -0600

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

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

Apparently, building Sage from scratch on the system will resolve this issue, but I have not tried that yet.

edit flag offensive delete link more


oh well... I guess I better figure out how to build this thing then.

martinB gravatar imagemartinB ( 2012-06-09 08:42:01 -0600 )edit

Not at all! Look in 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.

kcrisman gravatar imagekcrisman ( 2012-06-09 15:05:40 -0600 )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: 2012-06-09 05:40:06 -0600

Seen: 219 times

Last updated: Jun 09 '12