On Mon, Nov 18, 2019 at 10:12:52PM +, Matt Caswell wrote:
>
>
> On 18/11/2019 21:48, Dr. Matthias St. Pierre wrote:
> > The last 19 commits on https://github.com/openssl/openssl/commits/master,
> > starting from Nov 14 have a red cross from the CIs. What's going on again?
> > My personal impr
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.