Post the Sage_crash_report.txt

On Saturday, September 26, 2015 at 11:50:15 AM UTC+2, Juan Luis Varona 
wrote:
>
> Unfortunately, the compiling process of sage 6.9rc0 with xcode 7 under 
> macosx 10.11 has finished with errors: 
>
> ————————————— 
>
> ------------------------------------------------------------------------ 
> Unhandled SIGSEGV: A segmentation fault 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. 
> ------------------------------------------------------------------------ 
> /Applications/sage-6.9.rc0/build/bin/sage-logger: line 32: 97809 
> Segmentation fault: 11  ./sage --docbuild --no-pdf-links all html 
> make[2]: *** [doc-html] Error 139 
> make[1]: *** [all] Error 2 
>
> real        673m6.573s 
> user        583m48.760s 
> sys        71m8.235s 
> *************************************************************** 
> Error building Sage. 
>
> The following package(s) may have failed to build (not necessarily 
> during this run of 'make all'): 
>
> The build directory may contain configuration files and other potentially 
> helpful information. WARNING: if you now run 'make' again, the build 
> directory will, by default, be deleted. Set the environment variable 
> SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this. 
>
> make: *** [all] Error 1 
>
> ————————————— 
>
> This is the complete log file (23 megas file): 
>
> https://dl.dropboxusercontent.com/u/8293746/log-compiling-sage69rc0-xcode7-macosx10.11.txt
>  
>
> And this is what I obtain executing sage: 
>
>
> ┌────────────────────────────────────────────────────────────────────┐ 
> │ SageMath Version 6.9.rc0, Release Date: 2015-09-25                 │ 
> │ Type "notebook()" for the browser-based notebook interface.        │ 
> │ Type "help()" for help.                                            │ 
> └────────────────────────────────────────────────────────────────────┘ 
> ┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓ 
> ┃ Warning: this is a prerelease version, and it may be unstable.     ┃ 
> ┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛ 
> This looks like the first time you are running Sage. 
> Updating various hardcoded paths... 
> (Please wait at most a few minutes.) 
> DO NOT INTERRUPT THIS. 
> Done updating paths. 
>
> ********************************************************************** 
>
> 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: 
>         '/Users/jvarona/.sage/ipython_genutils-0.1.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 sage-s...@googlegroups.com 
> <javascript:> 
> 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' sage-s...@googlegroups.com <javascript:> < 
> /Users/jvarona/.sage/ipython_genutils-0.1.0/Sage_crash_report.txt 
>
> To ensure accurate tracking of this issue, please file a report about it 
> at: 
> http://trac.sagemath.org 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to