By the way, the problem persists no matter whether the .sobj file was created using sage 6.8 or 7.3.
On Thursday, September 8, 2016 at 4:35:13 PM UTC+2, Stan wrote: > > Thanks for correcting the link. The .sobj file was generated by > save_session(), and contains several dictionaries, variable definitions > etc. I did actually recreate it in sage 7.3 as I thought it might have been > a compatibility issue with sage 6.8, so if it is corrupt, there is some > problem that appeared some time between ver. 6.8 and 7.x. > > On Thursday, September 8, 2016 at 3:53:57 PM UTC+2, vdelecroix wrote: >> >> The download link is >> >> >> https://cloud.sagemath.com/34b4b62a-2621-47c8-9bda-cde3a855f995/raw/leaf_chamber_eqs_PM.sobj >> >> >> (the link by the OP is a HTML page that displays the content of the file) >> >> There seems to be a problem with the content of your >> leaf_chamber_eqs_PM.sobj file. Namely the dictionary is in some invalid >> state. >> >> sage: a = load('/tmp/leaf_chamber_eqs_PM.sobj') >> sage: type(a) # this should not fail!! >> <type 'dict'> >> --------------------------------------------------------------------------- >> >> TypeError Traceback (most recent call >> last) >> <ipython-input-7-5228b2754e89> in <module>() >> ----> 1 type(a) >> >> ...IPython/core/displayhook.pyc in __call__(self, result) >> 244 self.start_displayhook() >> 245 self.write_output_prompt() >> --> 246 format_dict, md_dict = >> self.compute_format_data(result) >> 247 self.update_user_ns(result) >> 248 self.fill_exec_result(result) >> >> .../IPython/core/displayhook.pyc in compute_format_data(self, result) >> 148 >> 149 """ >> --> 150 return self.shell.display_formatter.format(result) >> 151 >> 152 # This can be set to True by the write_output_prompt method >> in a subclass >> >> .../sage/repl/display/formatter.pyc in format(self, obj, include, >> exclude) >> 158 # First, use Sage rich output if there is any >> 159 PLAIN_TEXT = u'text/plain' >> --> 160 sage_format, sage_metadata = self.dm.displayhook(obj) >> 161 assert PLAIN_TEXT in sage_format, 'plain text is always >> present' >> 162 if sage_format.keys() != [PLAIN_TEXT]: >> >> TypeError: 'NoneType' object is not iterable >> >> Vincent >> >> On 08/09/16 15:42, Stan wrote: >> > Dear all, >> > >> > I am on debian jessy 64bit and after installing sage 7.3 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 >> >> > >> > 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) >> > print eq_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.
