Ask Your Question

martinB's profile - activity

2018-08-31 20:30:09 -0500 received badge  Notable Question (source)
2018-08-31 20:30:09 -0500 received badge  Popular Question (source)
2015-01-13 13:58:40 -0500 received badge  Notable Question (source)
2015-01-13 13:58:40 -0500 received badge  Popular Question (source)
2012-12-27 10:40:56 -0500 received badge  Student (source)
2012-12-16 04:19:43 -0500 asked a question How to point the Mac 'app' at a different sage source tree

What are the steps to point an installed /Applications/Sage.app to a different source tree. Currently I guess it points at /Applications/Sage.app/Contents/Resources/sage, Ivan's answer to another question seems to suggest that it can be redirected easily but did not give any details.

2012-06-09 08:42:01 -0500 commented answer Should evaluating 1.0e-15 produce an Unhandled SIGILL

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

2012-06-09 08:41:05 -0500 received badge  Scholar (source)
2012-06-09 08:41:05 -0500 marked best answer Should evaluating 1.0e-15 produce an Unhandled SIGILL

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.

2012-06-09 06:22:50 -0500 received badge  Editor (source)
2012-06-09 05:43:14 -0500 received badge  Organizer (source)
2012-06-09 05:40:06 -0500 asked a question Should evaluating 1.0e-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.
------------------------------------------------------------------------