On Thu, May 09, 2019 at 02:19:26PM +0200, Maciej Zdeb wrote:
> Hi Willy,
> I've built 1.9 from head, unfortunately something is wrong, right now I've
> got segfault:
> Core was generated by `/usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p
> /var/run/haproxy.pid -D -sf 75'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x0000000000484ab4 in h2_process_mux (h2c=0x1cda990) at
> src/mux_h2.c:2609
> 2609        list_for_each_entry_safe(h2s, h2s_back, &h2c->send_list, list) {
> (gdb) bt f
> #0  0x0000000000484ab4 in h2_process_mux (h2c=0x1cda990) at
> src/mux_h2.c:2609
>         h2s = 0x2

So now we have the proof that the memory is corrupted! Olivier thinks
he found a possible culprit one hour ago, which could cause a detached
stream to stay referenced, and thus to corrupt the lists. I'm unsure
to what extent it can cause the presence of a dead stream in this list,
but from the beginning we're seeing wrong stuff there in your reports
and it affects the same list :-/  For reference the commit ID in 1.9
is 07a9f0265 ("BUG/MEDIUM: h2: Make sure we set send_list to NULL in
h2_detach()."). I hope that's not what you're running so that there's
still some hope. Care to double-check ?


Reply via email to