Ask Your Question

BCWDave's profile - activity

2018-04-25 09:36:00 -0500 received badge  Nice Answer (source)
2018-04-23 22:59:47 -0500 asked a question Do Sage distribution binaries support running on multiple cores?

Running Sage for some complex matrix operations that take a long time to run. Looking at the system monitor it is pretty clear that Sage is only using 1 of 4 available cores on my processor. Is it possible with standard binaries (versus custom build) to have Sage use more than 1 core?

2018-04-23 05:10:48 -0500 received badge  Self-Learner (source)
2018-04-23 05:10:48 -0500 received badge  Teacher (source)
2018-04-23 00:00:26 -0500 answered a question What causes sage to crash as it starts?

Discovered that gfortran was not installed. Now appears that Sage is working!

2018-04-22 18:13:55 -0500 commented question What causes sage to crash as it starts?

The full crash report can be found here:

2018-04-21 17:04:29 -0500 received badge  Student (source)
2018-04-21 14:08:15 -0500 commented question What causes sage to crash as it starts?

Installation was from binaries - sage-7.6-Ubuntu_16.04-x86_64.tar.bz2 with target machine running Ubuntu 16.04 LTS.

Yes, a crash report was generated. Not sure how to upload the whole thing - 21KB Start of crash report has following:

Crash traceback:


ImportError Python 2.7.13: /sagemath/SageMath/local/bin/python Fri Apr 20 14:00:45 2018 A problem occurred executing Python code. Here is the sequence of function calls leading up to the error, with the most recent (innermost) call last.

2018-04-21 07:39:52 -0500 asked a question What causes sage to crash as it starts?

Installed sage 7.6 on Ubuntu 16.04 LTS to work with a colleague who is also on 7.X release (they are on Fedora). It all seemed to go OK but consistently get a crash message as soon as it starts. A crash report text file is created - can supply that for someone to look at.

Here is the terminal output:

┌────────────────────────────────────────────────────────────────────┐ │ SageMath version 7.6, Release Date: 2017-03-25 │ │ Type "notebook()" for the browser-based notebook interface. │ │ Type "help()" for help. │ └────────────────────────────────────────────────────────────────────┘

Oops, Sage crashed. We do our best to make it stable, but...

A crash report was automatically generated with the following information: - A verbatim copy of the crash traceback. - A copy of your input history during this session. - Data on your current Sage configuration.

It was left in the file named: '/home/davelautzenheiser/.sage/ipython-5.0.0/Sage_crash_report.txt' If you can email this file to the developers, the information in it will help them in understanding and correcting the problem.

You can mail it to: sage-support at with the subject 'Sage Crash Report'.

If you want to do it now, the following command will work (under Unix): mail -s 'Sage Crash Report' < /home/davelautzenheiser/.sage/ipython-5.0.0/Sage_crash_report.txt