Message 69133 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	Rhamphoryncus
Recipients	Rhamphoryncus, amaury.forgeotdarc, barry, benjamin.peterson, donmez, gvanrossum, jnoller, mark.dickinson, paulmelis, roudkerk, tebeka
Date	2008-07-02.22:00:44
SpamBayes Score	0.001686871
Marked as misclassified	No
Message-id	<aac2c7cb0807021500r3e3bee50geca2315440037060@mail.gmail.com>
In-reply-to	<1215035049.24.0.0836249156916.issue3088@psf.upfronthosting.co.za>

Content
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.

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.

History
Date	User	Action	Args
2008-07-02 22:00:45	Rhamphoryncus	set	spambayes_score: 0.00168687 -> 0.001686871 recipients: + Rhamphoryncus, gvanrossum, barry, amaury.forgeotdarc, tebeka, mark.dickinson, donmez, paulmelis, roudkerk, benjamin.peterson, jnoller
2008-07-02 22:00:44	Rhamphoryncus	link	issue3088 messages
2008-07-02 22:00:44	Rhamphoryncus	create