Adding a compile time check would be good. I’m not sure how.
It would be possible to implement a malloc failure feature in the test suite
that systematically runs a test many times, failing successive malloc calls.
I’m kind of surprised that the various static analysers hadn't found some of
Hello,
Observing a series of similar bugs related to a lack of checks of the
malloc return values, I wonder if we could automate the search of these
errors on the compile level (e.g. similar to the __owur macro)?
--
SY, Dmitry Belyavsky
