On Monday, December 31, 2012 11:41:32 AM UTC+1, Jean-Pierre Flori wrote: > > > > On Monday, December 31, 2012 11:33:25 AM UTC+1, Volker Braun wrote: >> >> If you want to use an external memory checker (like glibc MALLOC_CHECK_, >> electric fence, or valgrind) you still have to use SAGE_VALGRIND or python >> will use pymalloc. The latter has its own debugging code but is not >> transparent to external tools. >> >> export SAGE_VALGRIND=yes >> export SAGE_DEBUG=yes >> sage -f python-x.y.z.spkg >> >> My main problem here is not to change debugging options or allocators > used, but just to reproduce the bug in modules.pyx :) > If I cannot even get a segfault, having proper tools or not seems less > important. > > Anyway, I'm currently making four builds of sage-5.6.beta2 with the set of > patches from #13864 plus the patches from #13889 (and dependencies) with > all combinations of SAGE_VALGRIND and SAGE_DEBUG. > I completely missed #13566 but even with that I cannot reproduce the segfault reported there on 5.6.beta2 + #13864 + #13889 + #13566 + deps without SAGE_DEBUG and SAGE_VALGRIND.
-- 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.
