Thank you for the fast response! I can confirm that this patch indeed fixes the segfault.
Best, Leo Am Mo., 1. Apr. 2019 um 14:21 Uhr schrieb Ricardo Nabinger Sanchez <[email protected]>: > > Hi Leonhard, > > On Mon, 1 Apr 2019 13:14:06 +0200 > Leonhard Wimmer > <leonhard.wimmer+haproxy-pzuFaFavQ5/[email protected]> wrote: > > > I also managed to get a stack trace with the current haproxy-1.8 (a3cfe8f4): > > > > #0 tcpcheck_main (check=check@entry=0x555555746608) at src/checks.c:2774 > > #1 0x000055555561c464 in connect_conn_chk (t=0x55555575d1f0) at > > src/checks.c:1549 > > This segfault might be fixed with this commit: > > > http://git.haproxy.org/?p=haproxy.git;a=commit;h=4bccea98912c74fa42c665ec25e417c2cca4eee7 > > Cheers, > > -- > Ricardo Nabinger Sanchez http://www.taghos.com.br/ > >
