On Fri, May 04, 2012 at 07:31:46AM +0000, Simon King wrote: > On 2012-05-04, Simon King <simon.k...@uni-jena.de> wrote: > >> I guess I better try whether garbage collection is related. Or create a > >> hook, such that all occuring calls to Python functions or methods are > >> listed. > > Aha! When disabling garbage collection before the failing test and > enabling it afterwards, then the tests pass as well! > > I'll see whether I can make gc document what objects it collects. That > will hopefully tell me what object is causing the double free when being > deallocated. > > Anyway, I still wonder: Can't one use valgrind to detect those things? > > I tried > valgrind --log-file=... ./sage -t > devel/sage/sage/crypto/mq/mpolynomialsystem.py > and then "glibc detected" did show up on screen. But after interrupting > with Ctrl-c, the log file wasn't exactly helpful (just a handful of > lines).
Did you try ./sage -t -valgrind devel/sage/sage/.... ? You probably need either the valgrind optional spkg or just the sage.supp from it in local/lib/valgrind/sage.supp. Running "valgrind ./sage -t ...." will just debug the shell executing the sage script, not sage itself. (--trace-children=yes should get around that, by the way, but ./sage -t -valgrind would be preferable if that works.) -Willem Jan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
