![]() running with sage -t -gdb (yes, that's possible!) or sage -t -verbose does not trigger the problem.running the same examples in an interactive session does not trigger the problem. ![]() The segmentation fault happens reliably, but is hard to study because ![]() Sage -t "devel/sage-main/sage/misc/cachefunc.pyx" # Killed/crashed The doctested process was killed by signal 11 Sage -t "devel/sage-main/sage/misc/cachefunc.pyx"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |