Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit
Date
Msg-id 32361.1544752864@sss.pgh.pa.us
Whole thread Raw
In response to Valgrind failures in Apply Launcher's bgworker_quickdie() exit  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit
List pgsql-hackers
Thomas Munro <thomas.munro@enterprisedb.com> writes:
> Since libcrypto.so is implicated, Andres asked me off-list if my
> changes to random number state initialisation might be linked to
> skink's failures beginning 12 or 15 days ago.  It appears not, as it
> was green for several runs after that commit.
> ...
> It's Debian unstable, which could be a factor.  Bugs in glibc?

Has anyone tried to reproduce this on other platforms?

It'd be interesting to know which updates were applied to skink's
host before the first failing run.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Valgrind failures in Apply Launcher's bgworker_quickdie() exit
Next
From: Andres Freund
Date:
Subject: Re: Valgrind failures in Apply Launcher's bgworker_quickdie() exit