#13864: Configure Python with pydebug when SAGE_DEBUG is set
----------------------------------------------------------+-----------------
Reporter: jpflori | Owner:
jason
Type: task | Status:
needs_work
Priority: major | Milestone:
sage-pending
Component: misc | Resolution:
Keywords: python spkg | Work issues:
make sure Sage builds and starts
Report Upstream: N/A | Reviewers:
Volker Braun
Authors: Jean-Pierre Flori | Merged in:
Dependencies: #13865, #13867, #13868, #13876, #13832 | Stopgaps:
----------------------------------------------------------+-----------------
Comment (by nbruin):
Replying to [comment:77 SimonKing]:
> {{{
> sage -t -gdb -force_lib "devel/sage/sage/tests/benchmark.py"
> }}}
Yes, that traceback is consistent with what I was observing prior to my
ZODB upgrade. My guess is that if you step up to frame !#4 and execute
{{{
(gdb) p PyString_AsString(PyObject_Repr(op))
}}}
you'll see it's stumbling on a `BTree` object. Upgrading ZODB should do
the trick (i.e., download
from [http://pypi.python.org/pypi/ZODB3/3.10.5] and then run
{{{
./sage -sh
python setup.py install
}}}
The most immediate trigger is a garbage collection. ZODB had its own
weakref implementation which played tricks with the reference counts,
apparently confusing so checks activated by pydebug. It looks like they've
solved that in 3.10.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13864#comment:79>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
