Hi Thomas, hi all, > This is just wrong. No one wants to malloc() to _always_ terminate the > process. > As I said, you have to differentiate the cases.
Do you read this? http://article.gmane.org/gmane.comp.audio.jackit/19998 We have discussed this already a lot and the plan must be first to get an inprovement of the current code base. Even in small steps. If you want to do it, please go for it. My solution would be to check every malloc. If someone else is standing up... that's fine for me. > How would you make that guarantee? Do you know for sure, that your > fprintf(stderr, "HELP!"); won't call malloc() itself? A printf is pretty fine and you can look at the code. You can alloc reserve memory that you can free if malloc fails. Nonetheless this all is academical. Improvement in small steps is all a way better Then talking 5 years for the perfect solution. What's you vote? Leave it as it is? Best Regards, Carsten _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
