homepage

On Wed, Jul 2, 2008 at 3:44 PM, Mark Dickinson <report@bugs.python.org> wrote:
>
> Mark Dickinson <dickinsm@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.