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, opoplawski, peadar, vstinner
Date 2019-08-14.21:32:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565818374.03.0.188467063522.issue21131@roundup.psfhosted.org>
In-reply-to
Content
"I do think SIGSTKSZ*2=16k is far too small considering the fault handler could be running arbitrary python code,"

We are talking abou the faulthandler_user() function of Modules/faulthandler.c. It is implemented in pure C, it doesn't allocate memory on the heap, it uses a very small set of functions (write(), sigaction(), raise()) and it tries to minimize its usage of the stack memory.

It is very different than the traceback module which is implemented in pure Python.

faulthandler is really designed to debug segmentation fault, stack overflow, Python hang (like a deadlock), etc.
History
Date User Action Args
2019-08-14 21:32:54vstinnersetrecipients: + vstinner, bkabrda, opoplawski, markmcclain, peadar, justbennet
2019-08-14 21:32:54vstinnersetmessageid: <1565818374.03.0.188467063522.issue21131@roundup.psfhosted.org>
2019-08-14 21:32:54vstinnerlinkissue21131 messages
2019-08-14 21:32:53vstinnercreate