[issue10158] BadInternalCall running test_multiprocessing

2010-10-21 Thread Bob Halley
Bob Halley added the comment: I rebuilt using --with-pydebug and -O0 -g. It now triggers an assertion a bit earlier. test_finalize (__main__.WithProcessesTestFinalize) ... Assertion failed: (op->ob_refcnt == 0), function _PyTrash_destroy_chain, file Objects/object.c, line 2433 (gdb) bt

[issue10158] BadInternalCall running test_multiprocessing

2010-10-20 Thread Bob Halley
New submission from Bob Halley : For reasons not germane to this bug report, I was running a modified Python 2.7 where PyTrash_UNWIND_LEVEL in Include/object.h had been defined to 10 instead of 50. With such a python, running test_multiprocessing causes a BadInternalCall to be triggered at