Unfortunately, it is not a compile-time check...
I mean smth like
https://github.com/openssl/openssl/blob/ab5c77b4766e0992751d86560193ca42b49cf316/include/openssl/e_os2.h#L198-L202
but not sure it is applicable to external functions...
On Thu, Nov 21, 2019 at 1:42 PM Salz, Rich wrote:
>
>-
* 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.
It’s there; look crypto/mem.c, shouldfail() and FAILTEST.
More detail, from off-list discusson:
i=0
while : ; do
* 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.
It’s there; look crypto/mem.c, shouldfail() and FAILTEST.
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
