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 pitrou
Recipients dmalcolm, joshbressers, pitrou, vstinner
Date 2010-10-13.16:35:47
SpamBayes Score 6.65316e-05
Marked as misclassified No
Message-id <1286987744.3362.1.camel@localhost.localdomain>
In-reply-to <>
> You would be wise to avoid using heap storage once you're in the crash
> handler. From a security standpoint, if something has managed to
> damage the heap (which is not uncommon in a crash), you should not
> attempt to allocate or free heap memory.

As far as I can tell, the signal handler in the patch doesn't call
malloc() or free(), neither directly nor indirectly.
Date User Action Args
2010-10-13 16:35:48pitrousetrecipients: + pitrou, vstinner, dmalcolm, joshbressers
2010-10-13 16:35:47pitroulinkissue8863 messages
2010-10-13 16:35:47pitroucreate