Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-18 Thread Luke Seelenbinder
Good thoughts, Tim. I've created two Github issue: - https://github.com/haproxy/haproxy/issues/762 (segfault) - https://github.com/haproxy/haproxy/issues/763 (uuid config issue) Best, Luke — Luke

Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-17 Thread Tim Düsterhus
Luke, Am 17.07.20 um 17:55 schrieb Luke Seelenbinder: > To follow up on this—is it easier if I create this as a GitHub issue? > It will certainly not get lost in the depths of the email archive and it allows to easily link commits to issues and issues to commits just by mentioning the number in

Re: Segfault on 2.2.0 and UUID fetch regression

2020-07-17 Thread Luke Seelenbinder
To follow up on this—is it easier if I create this as a GitHub issue? I'm also not sure if it's related to https://github.com/haproxy/haproxy/issues/758 or not. Best, Luke — Luke Seelenbinder Stadia Maps | Founder stadiamaps.com > On 16 Jul

Segfault on 2.2.0 and UUID fetch regression

2020-07-16 Thread Luke Seelenbinder
Hi List, I just installed 2.2.0 (as packaged on haproxy.debian.net), and I'm experiencing almost instant segfaults on all canary machines (seems to be on the first handled request). I captured a core for debug purposes, but had to roll back as these machines serve production traffic. I can