#14059: Fix refcount/deallocation of integers
------------------------------+---------------------------------------------
Reporter: SimonKing | Owner: rlm
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-5.7
Component: memleak | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: | Stopgaps:
------------------------------+---------------------------------------------
Comment (by SimonKing):
Replying to [comment:35 jpflori]:
> Maybe we are just f***ing up with Python debug memory api.
>
> What Python rants about is that the first bytes before the actual object
ONE, which should have been allocated in PyObject_DebugMallocAPI and set
to FORBIDDENBYTE are in fact worth CLEANBYTE, which is what the debug
memory api sets for the space reserved for the object itself...
What is the problem with it? Can we prevent it? Does it make sense to
prevent it when we are not in debug mode?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14059#comment:40>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
