Some diff backtrace log when crashing. Program received signal SIGSEGV, Segmentation fault. 0x000055555562ff8a in __pool_get_from_cache (pool=0x555555a49680 <pool_base_start>) at include/common/memory.h:199 199 LIST_DEL(&item->by_pool); (gdb) bt #0 0x000055555562ff8a in __pool_get_from_cache (pool=0x555555a49680 <pool_base_start>) at include/common/memory.h:199 #1 __pool_get_first (pool=0x555555a49680 <pool_base_start>) at include/common/memory.h:216 #2 pool_alloc_dirty (pool=0x555555a49680 <pool_base_start>) at include/common/memory.h:259 #3 pool_alloc (pool=0x555555a49680 <pool_base_start>) at include/common/memory.h:273 #4 cs_new (conn=0x555555b13500) at include/proto/connection.h:624 #5 h1s_new_cs (h1s=0x555555aff450) at src/mux_h1.c:238 #6 h1s_create (h1c=h1c@entry=0x555555aff2d0, cs=<optimized out>, sess=<optimized out>, sess@entry=0x555555b214a0) at src/mux_h1.c:320 #7 0x0000555555632d9a in h1_init (conn=0x555555b13500, proxy=0x555555a95a00, sess=0x555555b214a0, input=<optimized out>) at src/mux_h1.c:418 #8 0x000055555568ee6f in conn_install_mux (sess=<optimized out>, prx=<optimized out>, ctx=0x0, mux=<optimized out>, conn=0x555555b13500) at include/proto/connection.h:836 #9 conn_install_mux_fe (ctx=0x0, conn=0x555555b13500) at include/proto/connection.h:1112 #10 conn_complete_session (conn=conn@entry=0x555555b13500) at src/session.c:447 #11 0x0000555555690138 in session_accept_fd (l=0x555555a977c0, cfd=15, addr=0x7fffffffdbf0) at src/session.c:286 #12 0x00005555556759e0 in listener_accept (fd=<optimized out>) at src/listener.c:965 #13 0x000055555569e7ed in fdlist_process_cached_events (fdlist=<optimized out>) at src/fd.c:452 #14 fd_process_cached_events () at src/fd.c:470 #15 0x00005555556054b6 in run_poll_loop () at src/haproxy.c:2474 #16 run_thread_poll_loop (data=<optimized out>) at src/haproxy.c:2503 #17 0x000055555557557b in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:3174
Program received signal SIGSEGV, Segmentation fault. 0x0000555555b14fd0 in ?? () (gdb) bt #0 0x0000555555b14fd0 in ?? () #1 0x00007ffff733cf61 in SSL_do_handshake () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #2 0x00005555555891aa in ssl_sock_handshake (conn=conn@entry=0x555555b14b80, flag=flag@entry=33554432) at src/ssl_sock.c:5490 #3 0x000055555568c084 in conn_fd_handler (fd=<optimized out>) at src/connection.c:88 #4 0x000055555569e7ed in fdlist_process_cached_events (fdlist=<optimized out>) at src/fd.c:452 #5 fd_process_cached_events () at src/fd.c:470 #6 0x00005555556054b6 in run_poll_loop () at src/haproxy.c:2474 #7 run_thread_poll_loop (data=<optimized out>) at src/haproxy.c:2503 #8 0x000055555557557b in main (argc=<optimized out>, argv=<optimized out>) at src/haproxy.c:3174 Regards, Alexander Liu On Sun, Apr 28, 2019 at 8:24 PM Alec Liu <[email protected]> wrote: > > Hi List, > > Got it. > This is how to reproduce the issue I mentioned. > > 1) I am using commit 4de0eba8488f7d7b471d60da76d815c69e44fecb, the > master branch; > 2) setup a tcp relay for HTTP as frontend and HTTPS as backend; > 3) make sure the HTTPS connection is working, when starting the haproxy; > 4) try to access the HTTP frontend, confirm it is working; > 5) then reroute the ip address of the HTTPS connection to a black > hole; (when I am using socks4 proxy for upstream will be easier to do > it, just turn the proxy off) > 6) try to access the HTTP frontend, then it crash. > > Please check the attached file for more details. > > Thank you. > > Regards, > Alexander Liu > > > On Sun, Apr 28, 2019 at 7:57 PM Tim Düsterhus <[email protected]> wrote: > > > > Alec, > > > > Am 28.04.19 um 09:51 schrieb Alec Liu: > > > When I am testing my patch which is base on the master branch, and > > > come across some crash causing by segmentation fault. > > > > > > And I have it retested without my patch applied, confirmed nothing to > > > do with my patch. > > > I have a quick test with the git tag v1.9.0 as well, looks like > > > working normally. > > > > > > I am wondering if I should report it or just leave it, since it is a > > > development branch issue. > > > > Yes, please do report it! In the worst case the issue is already known, > > in the best case it is not and you found a legitimate issue that would > > not have been found otherwise. So nothing to lose here. > > > > For a segmentation fault a full backtrace using gdb or valgrind would be > > helpful. The other things (config, haproxy -vv, etc. all apply as well). > > > > Best regards > > Tim Düsterhus
