I have both, one locally compiled version, which I upgraded from 7.x, and one freshly installed binary. Same problem on both. Seems that save_session() and load_session() causes all sorts of problems, especially when using jupyter.
On Thursday, September 8, 2016 at 11:45:32 PM UTC+2, leif wrote: > > Stan wrote: > > Dear all, > > > > I am on debian jessy 64bit and after installing sage 7.3 > > Does that mean you took a pre-built binary, or did you build from source? > > > -leif > > > I keep getting > > segfault for the same worksheets that run smoothly in sage 6.8. I have > > now managed to isolate a small example, which I uploaded to > > cloud.sagemath, where it does not give a segfault message, but just runs > > forever. To use locally, download this file: > > > > https://cloud.sagemath..com/projects/34b4b62a-2621-47c8-9bda-cde3a855f995/files/leaf_chamber_eqs_PM.sobj > > > < > https://cloud.sagemath.com/projects/34b4b62a-2621-47c8-9bda-cde3a855f995/files/leaf_chamber_eqs_PM.sobj> > > > > > > then run the following code in a sagenb notebook: > > | > > vdict =cdict.copy() > > vdict[a_s]=1 > > vdict[L_l]=0.07 > > vdict[P_a]=101325 > > vdict[P_wa]=20/1000*101325 > > vdict[R_s]=400 > > vdict[Re_c]=3000 > > vdict[T_a]=273+30 > > vdict[T_w]=vdict[T_a] > > vdict[g_sw]=0.15/40 > > vdict[v_w]=1. > > vdict[nu_a]=eq_nua.rhs().subs(vdict) > > printeq_Re.subs(vdict) > > | > > > > Here are the error messages I get in the terminal: > > > > 2016-09-08T15:04:22+0200 [stdout#info] raise > > NoFunctionNameInFrameError() > > 2016-09-08T15:04:22+0200 [stdout#info] NoFunctionNameInFrameError: C > > function name could not be determined in the current C stack frame > > 2016-09-08T15:04:22+0200 [stdout#info] close failed in file object > > destructor: > > 2016-09-08T15:04:22+0200 [stdout#info] IOError: [Errno 9] Bad file > > descriptor > > 2016-09-08T15:04:22+0200 [stdout#info] > > 2016-09-08T15:04:22+0200 [stdout#info] Saved trace to > > .../.sage/crash_logs/crash_XdQCv0.log > > 2016-09-08T15:04:22+0200 [stdout#info] > > ------------------------------------------------------------------------ > > 2016-09-08T15:04:22+0200 [stdout#info] Unhandled SIGABRT: An abort() > > occurred. > > 2016-09-08T15:04:22+0200 [stdout#info] This probably occurred because a > > *compiled* module has a bug > > 2016-09-08T15:04:22+0200 [stdout#info] in it and is not properly wrapped > > with sig_on(), sig_off(). > > 2016-09-08T15:04:22+0200 [stdout#info] Python will now terminate. > > 2016-09-08T15:04:22+0200 [stdout#info] > > ------------------------------------------------------------------------ > > > > I'm sure the example could be simplified much more, but I hope this > > helps to track down the problem. The worksheet can also be found on > > cloud.sagemath: > > > > > https://cloud.sagemath.com/projects/34b4b62a-2621-47c8-9bda-cde3a855f995/files/sigsegv_7.3.sagews > > > > -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
