Frédéric Lécaille

`[-Wstringop-overflow=]` ??? We do not know what was passed as argument to -Wstringop-overflow. Looks like a GCC bug. To me this warning must be ignored.

Hello @Tristan971, there is not enough information in the backtrace to have an idea about what could lead the watchdog to be triggered. It would be interesting to enable the...

Indeed there are chances this commit fixed this issue: ``` commit 0937ad2b864c8dfb96ab0435a7420dcc2d13f624 Author: Frédéric Lécaille Date: Wed Aug 24 17:57:09 2022 +0200 BUG/MINOR: quic: Stalled connections (missing I/O handler wakeup)...

No, you do not have to close it.

@hpn0t0ad hello. I would like to have a status about this issue please. I do not see any information about the pool allocations in the comments (perhaps they have been...

Sorry, but this trace is no sufficient to identify the root cause of this issue. You should try to enable the traces using a ring buffer adding this section to...

Please also consider using -O1 compilation option in place of -O2 to have more chance to get useful information from the backtrace. This gdb command would also give us more...

Compress the file and attach the result to this issue please.

Thank you for these useful traces. @wtarreau here is a patch which should fix this issue. https://github.com/haproxytech/quic-dev/commit/09f0c64c3bc2cb723d3c34f30f6f05b716732e11

hello, when we get such traces, the risk is that the connection may block. Is it the case?