John Bollinger <john.bollin...@stjude.org> added the comment:
I was already working on a standalone test, and now I have it ready. Using it
I can demonstrate the issue against both the cpython trunk and against my local
v2.6.6 binary distribution, therefore I have added v3.3 as an affected version.
It is reasonable to suppose that all versions in between are affected as well,
but I have not tested versions 2.7, 3.1, or 3.2.
I attach a complete package with source and Autotools build scripts. A bit of
overkill, I guess, but pretty easy to use. As is typical with the Autotools,
the build system is far larger than the actual project sources (those are only
162 lines of C and 57 lines of Python, both reasonably well commented).
The test should be run against a Python configured with --enable-shared
--with-threads (I also used --with-pydebug), and that can be an uninstalled
working copy. To build and perform the test:
1) Unpack the tarball
tar xzf deadlocktest-0.2.tar.gz
2) Change to the test source directory
cd deadlocktest-0.2
3) Configure the test for building
./configure [--with-python-build=/path/to/working/copy]
4) Build the test
make
5) Run the test
make check
The test builds and runs (and fails) against both Python 2.6 and the current
trunk (3.3). It passes when run against my patched versions of 2.6 and 3.3.
----------
versions: +Python 3.3
Added file: http://bugs.python.org/file25032/deadlocktest-0.2.tar.gz
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue14390>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
