Hi Amicalement, >> Nonetheless: Malloc can fail and we have to take care of that. > But when it fails, what *can* you do apart from trying to fail as > gracefully as possible? And failing gracefully is impossible for an > embedded target cross-debugger.
Well, on Windows you get a ugly message box that is interpreted by the user as "developers don't do there job right". The other thing is that you have the chance to report the error to the user. You can probably also send a message over the network, so that the user see in the telnet session what's going wrong, ...... . Nonetheless, if most of the developers think that it is not necessary and there is a vote for "not to check" and accept the ugly message box, then it have to be at least documented at the malloc call. As i said before, i come from the automotive world and the "stop at every single error" mentality is the worst and dumbest scenario. In most cases, there are smarter solutions. Best Regards, Carsten _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
