For what it's worth, I'm working on allowing debugging to initiated from within doctesting. But it's not ready yet.
I'm stuck on the redirection of standard out; I've started another thread to see if anyone has ideas. David On Thu, May 3, 2012 at 3:10 PM, Simon King <simon.k...@uni-jena.de> wrote: > Hi Martin, > > On 2012-05-03, Martin Albrecht <martinralbre...@googlemail.com> wrote: > >> Anyway. What tools are recommended for tracking the problem down? I > >> tried valgrind, but when I interrupted the test with Ctrl-c (which is > >> necessary because it hangs after reporting the double free), there > >> seems to be no output from valgrind. > > > > I'd try to find a way to reproduce it outside of the doctest framework > and > > then try to make it crash with sage -gdb. > > I did try. I ran the test in --verbose mode, and it turned out that the > crash > already occurs after 6 commands (including > change_warning_output(sys.stdout)). > > However, when I give the same commands in an interactive session (without > change_warning_output(sys.stdout), since I don't know where to import > that from), there is no crash. That's not good for debugging. I could > try to control garbage collection, though. Perhaps that's triggering the > crash. > > Cheers, > Simon > > > -- > 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 > -- 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
