[issue3088] test_multiprocessing hangs on OS X 10.5.3

Adam Olsen report at bugs.python.org
Thu Jul 3 00:00:45 CEST 2008

Adam Olsen <rhamph at gmail.com> added the comment:

On Wed, Jul 2, 2008 at 3:44 PM, Mark Dickinson <report at bugs.python.org> wrote:
> Mark Dickinson <dickinsm at gmail.com> added the comment:
>> Mark, can you try commenting out _TestCondition and seeing if you can
>> still get it to hang?;
> I removed the _TestCondition class entirely from test_multiprocessing,
> and did make test again.  It didn't hang! :-)  It crashed instead.  :-(

Try running "ulimit -c unlimited" in the shell before running the test
(from the same shell).  After it aborts it should dump a core file,
which you can then inspect using "gdb ./python core", to which "bt"
will give you a stack trace ("backtrace").

On a minor note, I'd suggest running "./python -m test.regrtest"
explicitly, rather than "make test".  The latter runs the test suite
twice, deleting all .pyc files before the first run, to detect
problems in their creation.

Python tracker <report at bugs.python.org>

More information about the Python-bugs-list mailing list