Hi David, > As I understand it, ANSI C says it returns NULL when it can't > allocate memory. Anything else would be phenominally rude.
You don't follow the thread, right? You don't read the people who said it is a bad idea to check the result ;-)? Alex and some others came up with the point, that on linux malloc doesn't come back anymore and send instead a sigterm. He posted this link: http://article.gmane.org/gmane.comp.audio.jackit/19998 I have just checked that out and this is NOT TRUE on my linux machine with Fedora Core 11. > For the record, I've never heard of *ANY* runtime environment where a > malloc()/calloc()/... failure aborts the program. Well.. yesterday people said that right here on the list. Best Regards, Carsten _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
