tag:blogger.com,1999:blog-3024470480937744884.post6106072328228922161..comments2024-03-18T04:40:58.042-07:00Comments on Security: Some Python bugsChris Evanshttp://www.blogger.com/profile/01004765479735675808noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-3024470480937744884.post-64556814332786708372009-01-23T13:22:00.000-08:002009-01-23T13:22:00.000-08:00I have to admit I was really happy to see people b...I have to admit I was really happy to see people both from Google and Apple kinda run with the concept, which was more of what I wanted to do honestly.<BR/><BR/>On a side note, I believe (going from memory) the error messages printed out by malloc.c et al on failure use constant strings and stack memory for the most part-- it goes into __libc_message() which is pretty involved and I won't say is safe because I've never followed it back down, but from what I recall there were a lot of alloca() calls and such, so in theory, assuming that is consistent, theres no usage of heap memory during fatal errors.not_mehttps://www.blogger.com/profile/05206789608401464729noreply@blogger.com