Hello, I'm spamming a lot these days :)
I found a strange coredump on HAProxy 2.0.14 that started a few days ago for no reason. It's not a coredump but a raise(). Stacktrace : #0 0x00007fde8c9f8495 in raise () from /lib64/libc.so.6 #1 0x00007fde8c9f9c75 in abort () from /lib64/libc.so.6 #2 0x00007fde8ca363a7 in __libc_message () from /lib64/libc.so.6 #3 0x00007fde8ca3bdee in malloc_printerr () from /lib64/libc.so.6 #4 0x00007fde8ca3ec3d in _int_free () from /lib64/libc.so.6 #5 0x000000000047a885 in ssl_sock_free_ssl_conf () at src/ssl_sock.c:3740 #6 0x000000000047bdd2 in ssl_sock_free_all_ctx () at src/ssl_sock.c:5063 #7 0x000000000047c301 in ssl_sock_destroy_bind_conf () at src/ssl_sock.c:5095 #8 0x000000000050c8fb in deinit () at src/haproxy.c:2533 #9 0x000000000050dc3f in main () at src/haproxy.c:3449 This seems to happen when issuing the following command : 'set ssl ocsp-response xxx' |socat stdio /var/run/haproxy.sock This is the first time I see such a behaviour :/ I can provide a "bt full" output privately if needed. HAProxy build options: Build options : TARGET = linux-glibc CPU = generic CC = gcc CFLAGS = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv -Wno-unused-label -Wno-sign-compare -Wno-unused-parameter -Wno-old-style-declaration -Wno-ignored-qualifiers -Wno-clobbered -Wno-missing-field-initializers -Wtype-limits OPTIONS = USE_THREAD=0 USE_STATIC_PCRE=1 USE_OPENSSL=1 USE_LUA=1 USE_ZLIB=1 USE_NS= Built with OpenSSL version : OpenSSL 1.1.1g 21 Apr 2020 Olivier
