Re: segfault using wrong table

On Mon, Jun 06, 2016 at 04:45:49PM +0200, Thierry FOURNIER wrote: > Thank you for the bug repport. The patch in attachment fix this > behaviour. Can you try it ? I join a fix for current dev and 1.6 > version and other one for the 1.5 version. So I've applied your patch to 1.7 and 1.6, I'll

Re: segfault using wrong table

Hi, 2016-06-06 17:19 GMT+02:00 Willy Tarreau: > Hi guys, > > On Mon, Jun 06, 2016 at 04:45:49PM +0200, Thierry FOURNIER wrote: >> Hi, >> >> Thank you for the bug repport. The patch in attachment fix this >> behaviour. Can you try it ? I join a fix for current dev and 1.6 >> version and other one

Re: segfault using wrong table

On Mon, Jun 06, 2016 at 05:38:58PM +0200, Kay wrote: > Hi, > > 2016-06-06 17:19 GMT+02:00 Willy Tarreau: > > Hi guys, > > > > On Mon, Jun 06, 2016 at 04:45:49PM +0200, Thierry FOURNIER wrote: > >> Hi, > >> > >> Thank you for the bug repport. The patch in attachment fix this > >> behaviour. Can

Re: segfault using wrong table

Hi guys, On Mon, Jun 06, 2016 at 04:45:49PM +0200, Thierry FOURNIER wrote: > Hi, > > Thank you for the bug repport. The patch in attachment fix this > behaviour. Can you try it ? I join a fix for current dev and 1.6 > version and other one for the 1.5 version. That's very interesting. I indeed

Re: segfault using wrong table

Hi, Thank you for the bug repport. The patch in attachment fix this behaviour. Can you try it ? I join a fix for current dev and 1.6 version and other one for the 1.5 version. Thierry Fournier On Mon, 6 Jun 2016 11:36:52 +0200 Kay wrote: > Hi, > > i've been playing

segfault using wrong table

Hi, i've been playing around with stick-tables and seeing a segfault using a false table on the first request with the following simplified configuration: defaults mode http timeout connect 10s timeout client 60s timeout server 60s frontend www bind :8080 tcp-request