On May 2, 2:04 pm, William Stein <wst...@gmail.com> wrote:
> On Sat, May 2, 2009 at 8:53 AM, Alessandro Torre
<SNIP>
> > Is it possible that my processor is obsolete for this version of Sage?
>
> Yes.
>
> What is the output of
>
> cat /proc/cpuinfo
I doubt this will be helpful. Having thought about this for a while my
guess is that some of the instructions used in MPIR might cause this.
When I wrote a script to detect "advanced" instructions I only
concentrated on SSE instructions since back then it was the major (and
only known) problem. If gdb is installed in the VMWare image we can
start Sage under gdb, get a back trace (to figure out which library it
is) and then disassemble around the current pc so that I can fix
this :)
So far no one has provided information to what is wrong, i.e. which
instruction[s] in what library causes this, so I cannot even start to
fix this.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
