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 christian.heimes, neologix, pitrou, vstinner
Date 2014-04-29.06:01:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398751272.44.0.501848815887.issue21037@psf.upfronthosting.co.za>
In-reply-to
Content
I'd like to move this forward: it could IMO be a great way to proactively detect potential security defects, and nasty stack/heap/memory corruption in general.

The remaining - missing - part is buildbot integration: AFAICT the only specific thing to do is to start the process with the ASAN_OPTIONS environment variable set to "handle_segv=0", to avoid interference with faulthandler.

But I'm not really familiar with the buildbot support, so if anyone has a clue...
History
Date User Action Args
2014-04-29 06:01:12neologixsetrecipients: + neologix, pitrou, vstinner, christian.heimes
2014-04-29 06:01:12neologixsetmessageid: <1398751272.44.0.501848815887.issue21037@psf.upfronthosting.co.za>
2014-04-29 06:01:12neologixlinkissue21037 messages
2014-04-29 06:01:11neologixcreate