Message 192336 - 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	vstinner
Recipients	Leeward, christian.heimes, docs@python, r.david.murray, vstinner
Date	2013-07-05.17:02:58
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1373043778.89.0.186403416859.issue18356@psf.upfronthosting.co.za>
In-reply-to

Content
> For a full trackdown and workaround of the problem see http://stackoverflow.com/questions/17344974/python-helpnumpy-causes-segfault-on-exit The gdb trace is not interesting because it stopped at SIGPIPE, which is not an error. Please rerun your program in gdb and ignore SIGPIPE (type "handle SIGPIPE noprint nostop") or continue on PIPE (type "cont"). Then when you get the crash, please copy/paste the gdb traceback here.

> For a full trackdown and workaround of the problem see http://stackoverflow.com/questions/17344974/python-helpnumpy-causes-segfault-on-exit

The gdb trace is not interesting because it stopped at SIGPIPE, which is not an error. Please rerun your program in gdb and ignore SIGPIPE (type "handle SIGPIPE noprint nostop") or continue on PIPE (type "cont"). Then when you get the crash, please copy/paste the gdb traceback here.

History
Date	User	Action	Args
2013-07-05 17:02:58	vstinner	set	recipients: + vstinner, christian.heimes, r.david.murray, docs@python, Leeward
2013-07-05 17:02:58	vstinner	set	messageid: <1373043778.89.0.186403416859.issue18356@psf.upfronthosting.co.za>
2013-07-05 17:02:58	vstinner	link	issue18356 messages
2013-07-05 17:02:58	vstinner	create