[issue10158] BadInternalCall running test_multiprocessing

2013-11-18 Thread STINNER Victor
STINNER Victor added the comment: Even with PyTrash_UNWIND_LEVEL in Include/object.h defined to 10 instead of 50, I cannot reproduce the issue on the 2.7 branch of Mercurial. I guess that the bug was already fixed in Python 2.7 and this issue has no activity since 3 years, so I'm closing it.

[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 #0

[issue10158] BadInternalCall running test_multiprocessing

2010-10-20 Thread R. David Murray
Changes by R. David Murray : -- nosy: +asksol ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue10158] BadInternalCall running test_multiprocessing

2010-10-20 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: Does it happen when compiled in debug mode? There may be asserts that will give a better (or earlier) error message. Some thoughts: the '_PyTrash_delete_later' chain can only contain a limited set of objects: lists, frames... (which code contain the Py_

[issue10158] BadInternalCall running test_multiprocessing

2010-10-20 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- assignee: -> jnoller nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[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 li