Yes, it’s likely this is due to the amount of memory available in the machine. I tried to use reasonable values, but apparently not reasonable enough.
This is certainly a case where we’re trying to stretch the limits of the hardware; so it may not be an appropriate test for all hardware. In the case below, the call to mmap() failed, and there’s an OPENSSL_assert() there that’s probably not necessary; the error condition checked by the assert is handled safely. This is different than the problem <u...@ll.mit.edu<mailto:u...@ll.mit.edu>> was seeing, which is likely a condition where memory is being maxed out. -- -Todd Short // tsh...@akamai.com<mailto:tsh...@akamai.com> // "One if by land, two if by sea, three if by the Internet." On May 12, 2017, at 2:51 PM, Salz, Rich via openssl-dev <openssl-dev@openssl.org<mailto:openssl-dev@openssl.org>> wrote: Current master 1d0f116 fails on my machine. ../test/recipes/90-test_secmem.t .. 1..1 # Subtest: ./secmemtest 1..1 # INFO: @ test/secmemtest.c:65 # Possible infinite loop: allocate more than available # INFO: @ test/secmemtest.c:71 # Possible infinite loop: small arena # INFO: @ test/secmemtest.c:79 # Possible infinite loop: 1<<31 limit crypto/mem_sec.c:428: OpenSSL internal error: assertion failed: sh.map_result != MAP_FAILED ../util/shlib_wrap.sh ./secmemtest => 134 not ok 1 - running secmemtest -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
