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 bkabrda, justbennet, markmcclain, miss-islington, opoplawski, peadar, vstinner
Date 2019-08-19.10:13:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566209620.77.0.332029074062.issue21131@roundup.psfhosted.org>
In-reply-to
Content
> Its interesting to read the comment on the IA64 definition for SIGSTKSZ:

Python doesn't support IA64 architecture.

Note: I'm not sure that this architecture is going to survive in the long term... More and more systems stopped to support it.


> Well, one argument for the dynamic approach is that existing python
binaries can adjust without needing to be respun for new CPUs.

PR 13649 gets the default thread stack size, it doesn't get SIGSTKSZ. I expect a thread stack size to be way larger than SIGSTKSZ.

For on my Fedora 30 (Linux kernel 5.1.19-300.fc30.x86_64, glibc-2.29-15.fc30.x86_64) on x86-64, SIGSTKSZ is just 8 KiB (8192 bytes) whereas pthread_attr_getstacksize() returns 8 MiB (8388608 bytes).

As I already wrote, using 8 MiB instead of 8 KiB looks like a waste of memory: faulthandler is only useful for stack overflow, which is a very unlikely bug.
History
Date User Action Args
2019-08-19 10:13:40vstinnersetrecipients: + vstinner, bkabrda, opoplawski, miss-islington, markmcclain, peadar, justbennet
2019-08-19 10:13:40vstinnersetmessageid: <1566209620.77.0.332029074062.issue21131@roundup.psfhosted.org>
2019-08-19 10:13:40vstinnerlinkissue21131 messages
2019-08-19 10:13:40vstinnercreate