9b35afd6ac
gcc 4.8 vs 5.2 seem to compile eloop_register_sock() differently. With 5.2, that function name does not show up in the backtrace since eloop_sock_table_add_sock() is used without a separate function call. This broke the memory allocation failure checking in this test case. Fix this by matching against the eloop_sock_table_add_sock() function which shows up in the backtrace for both gcc versions. Signed-off-by: Jouni Malinen <j@w1.fi> |
||
|---|---|---|
| .. | ||
| ap-mgmt-fuzzer | ||
| eapol-fuzzer | ||
| hwsim | ||
| p2p-fuzzer | ||
| wnm-fuzzer | ||
| .gitignore | ||
| Makefile | ||
| test-aes.c | ||
| test-asn1.c | ||
| test-base64.c | ||
| test-https.c | ||
| test-list.c | ||
| test-md4.c | ||
| test-milenage.c | ||
| test-rc4.c | ||
| test-rsa-sig-ver.c | ||
| test-sha1.c | ||
| test-sha256.c | ||
| test-x509.c | ||
| test-x509v3.c | ||
| test_x509v3_nist.sh | ||
| test_x509v3_nist2.sh | ||