undefined references since newlib-3.2.0
Josef Wolf
jw@raven.inka.de
Fri Jun 12 22:50:13 GMT 2020
On Fri, Jun 12, 2020 at 10:21:11AM +0200, Josef Wolf wrote:
> To be honest, I completely fail to understand how this commit
> https://sourceware.org/git?p=newlib-cygwin.git;a=commit;h=f88aece242178ff0c187d56e34a79645fbc44a23
> can possibly cause those link failures. After all,
> f88aece242178ff0c187d56e34a79645fbc44a23 shows no traces of abort/exit/kill/getpid.
This patch replaces Balloc() by eBalloc() which calls __assert_func() on
failure which in turn calls exit() and/or abort()
Is this really a sane thing to do? After all, assertions should be used to
detect logically impossible situations but not as a general replacement for
error handling.
Shouldn't those library functions simply report the error by returning NULL to
the caller and let the application handle the situation?
--
Josef Wolf
jw@raven.inka.de
More information about the Newlib
mailing list