On Monday, December 24, 2012 3:04:55 PM UTC+1, Jean-Pierre Flori wrote: > > > > On Monday, December 24, 2012 2:23:24 PM UTC+1, Volker Braun wrote: >> >> Does anybody have an explanation why this segfaults while importing >> Twisted? You are doctesting sage/modules/module.pyx, that shouldn't have >> anything to do with web servers or internet access. > > I think that is because the segfault occurs while quitting Sage, so this > involves all Python parts of Sage which have been used. > (Not sure is loaded at startup when doctesting, but you can find some > specific code involving and importing Twisted in qui_sage() in sage/all.py.) > Just a hint to continue debug that (unless someone wants to rewrite ALL of Sage): it might be helpful to rebuild python with --without-pymalloc to get more hindisghtful backtraces and valgrind output, just as suggested by the Python spkg. You can automagically do this by exporting SAGE_VALGRIND=yes and reinstalling Python.
-- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
