[issue26810] inconsistent garbage collector behavior across platforms when using ctypes data-structures
Martin Panter
report at bugs.python.org
Wed Apr 20 19:27:40 EDT 2016
Martin Panter added the comment:
You should write your program so that it does not release objects until they are no longer needed, then it can handle the garbage collector running at any time. But it is not clear to me what your offending null pointer is. Your code has lots of pointers that could be null.
Can you provide a complete demonstration, perhaps using a standard function such as libc.printf, rather than your arbitrary function?
----------
nosy: +martin.panter
stage: -> test needed
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue26810>
_______________________________________
More information about the Python-bugs-list
mailing list