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 neologix
Recipients neologix, rpointel, vstinner
Date 2011-08-31.17:30:09
SpamBayes Score 7.024131e-06
Marked as misclassified No
Message-id <1314811810.44.0.480222297433.issue12868@psf.upfronthosting.co.za>
In-reply-to
Content
OpenBSD's threads are userland threads, and sigaltstack() doesn't work when the program is built with -pthread:
http://marc.info/?l=openbsd-bugs&m=114323355014696&w=2

Note that POSIX warns about this:
http://www.opengroup.org/onlinepubs/000095399/functions/sigaltstack.html
""""
Use of this function by library threads that are not bound to
kernel-scheduled entities results in undefined behavior.
"""

I think we should skip this test on OpenBSD when Python is compiled with threads support.
Out of curiosity, could you try this:
$ ./python -c "import faulthandler; faulthandler.enable(); faulthandler._stack_overflow()"; echo $?

And if you're motivated, you could try it again after having built python with './configure --without-threads'.
History
Date User Action Args
2011-08-31 17:30:10neologixsetrecipients: + neologix, vstinner, rpointel
2011-08-31 17:30:10neologixsetmessageid: <1314811810.44.0.480222297433.issue12868@psf.upfronthosting.co.za>
2011-08-31 17:30:09neologixlinkissue12868 messages
2011-08-31 17:30:09neologixcreate