Hi Sébastien, On Wed, Jan 20, 2010 at 12:41 AM, slabbe <sla...@gmail.com> wrote:
<SNIP> > How should I debug this? Should I use valgrind? If you're going the Valgrind route, note that the optional Valgrind spkg was recently upgraded to version 3.5.0. See ticket #7440 [1]. You can grab the updated Valgrind spkg [2] from the Sage website. > Would it be possible > for "sage -t" to give more informations like which doctests caused the > mysterious error? Can you try "sage -t -verbose"? [1] http://trac.sagemath.org/sage_trac/ticket/7440 [2] http://www.sagemath.org/packages/optional/valgrind-3.5.0.p0.spkg -- Regards Minh Van Nguyen
-- 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
