[Python-Dev] negative ref count on windows debug version (original) (raw)
Amaury Forgeot d'Arc amauryfa at gmail.com
Fri Jan 20 22:42:20 CET 2012
- Previous message: [Python-Dev] negative ref count on windows debug version
- Next message: [Python-Dev] cpython (3.2): Avoid the compiler warning about the unused return value.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
2012/1/20 Dr.-Ing. Ingo D. Rullhusen <d01c at uni-bremen.de>
using
loc = PyDictNew(); PyXDECREF(loc); or PyObject *src = PyCompileString( code.toStdString().cstr(), "", Pysingleinput ); PyXDECREF(src); results in a "object at blahblah has negative ref count -1" error on windows visual studio in debug mode. And yes, python is compiled and linked in debug mode also. The release version seems to work. This happens in version 2.6.7 and 2.7.2.
This looks very unlikely. Python itself is written with tons of similar constructs, and works very well in debug mode. If you can isolate a reproducible case, please file a ticket on bugs.python.org, with all details: code, versions of the compiler, etc.
-- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20120120/39bcdba3/attachment.html>
- Previous message: [Python-Dev] negative ref count on windows debug version
- Next message: [Python-Dev] cpython (3.2): Avoid the compiler warning about the unused return value.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]