Re: segfault when using debug

Hi Matt,

On Wed, Apr 14, 2010 at 01:31:37PM +0100, Matt wrote: (...)
> 00000006:xxxxxxxxxxxxx.accept(0007)=0008 from [...........:38299]
> 00000006:xxxxxxxxxxxxx.clireq[0008:ffff]: POST ............ HTTP/1.1
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: User-Agent: curl/7.19.5
> (i486-pc-linux-gnu) libcurl/7.19.5 OpenSSL/0.9.8g zlib/1.2.3.3 libidn/1.15
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: Host: xxxxxxxxxx
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: ACCEPT: application/results+xml
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: Content-Length: 1180
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: Content-Type:
> application/x-www-form-urlencoded
> 00000006:xxxxxxxxxxxxx.clihdr[0008:ffff]: Expect: 100-continue
> 00000006:www.mydomain.com.srvrep[0008:0009]:
> /bin/bash: line 1: 12110 Segmentation fault /usr/sbin/haproxy -D -f
> /etc/haproxy/haproxy.cfg -p /var/run/haproxy.pid

Thanks for your config and reproducer. I could indeed reproduce the issue when accessing your server. It only happens in debug mode because we try to display invalid responses and in some cases we don't even find a beginning of message (in your case, due to the invalid request format, the server responded in HTTP/0.9 with pure HTML, without any status line nor header). The start-of-message pointer got dereferenced, causing the crash. I've fixed it, but the most important to me is that it only affected debug mode.

Best regards,
Willy Received on 2010/04/16 09:14