Hi Igor, On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote: > Hi guys, > > We are getting segfaults with haproxy 1.8.25 and thought I would ask if > this rings any bell: > > segfault at 5609a853ffff ip 00007f1b93928c10 sp 00007ffd5e731fd8 error 4 in > libc-2.19.so[7f1b9388e000+1be000]
At this point, no unfortunately. This could be a memcpy() on a NULL pointer or a use after free for example. > It is running on Ubuntu-14.04.2 (kernel 4.4.0-144-generic) and is happening > only on this particular one out of many dozens we have on Ubuntu-14.04 and > 16.04 > > I have attached strace so more details upon the next crash. I doubt you'll see much more using strace. You'd rather attach gdb to it and let it run. This way when it crashes again you can issue "bt full" and see the whole trace. It is even possible to force a core to be dumped from gdb for later inspection using "generate-core-file". Some people also know how to script it so that it automatically dumps and detaches upon crash, and limits the service interruption time, but I never remember how to do this, and the help embedded in it is next to inexistent :-/ Regards, Willy
