On Tue, Jun 19, 2018 at 4:30 PM William Lallemand <[email protected]> wrote: > That's interesting, we can suppose that this bug is not related anymore to the > signal problem we had previously. > Looks like it's blocking in the thread sync point. > Are you able to do a backtrace with gdb? that could help a lot.
yes, sorry, forgot to paste it. #0 0x000056269318f0fb in thread_sync_barrier (barrier=0x5626933fa528 <barrier.27104>) at src/hathreads.c:112 #1 thread_enter_sync () at src/hathreads.c:125 #2 0x00005626931377a2 in sync_poll_loop () at src/haproxy.c:2376 #3 run_poll_loop () at src/haproxy.c:2433 #4 run_thread_poll_loop (data=data@entry=0x5626a7aa1000) at src/haproxy.c:2463 #5 0x00005626930b3856 in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:3065 -- William
