On Wed, May 27, 2020 at 11:48:05AM +1000, Igor Cicimov wrote:
> Hi Willy,
>
> On Tue, May 26, 2020 at 4:43 PM Willy Tarreau wrote:
>
> > On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> > > We are getting segfaults with haproxy 1.8.25
> >
> > By the way, does this mean you didn't
Hi Willy,
On Tue, May 26, 2020 at 4:43 PM Willy Tarreau wrote:
> On Sun, May 24, 2020 at 10:35:10AM +1000, Igor Cicimov wrote:
> > We are getting segfaults with haproxy 1.8.25
>
> By the way, does this mean you didn't get them with a previous version
> (presumably 1.8.24) ? There aren't that
Hi Willy,
On Tue, May 26, 2020 at 4:31 PM Willy Tarreau wrote:
> 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 5609a853 ip
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 5609a853 ip 7f1b93928c10 sp 7ffd5e731fd8 error 4 in
>
Hi guys,
We are getting segfaults with haproxy 1.8.25 and thought I would ask if
this rings any bell:
segfault at 5609a853 ip 7f1b93928c10 sp 7ffd5e731fd8 error 4 in
libc-2.19.so[7f1b9388e000+1be000]
It is running on Ubuntu-14.04.2 (kernel 4.4.0-144-generic) and is happening
only on
5 matches
Mail list logo