Horton

Re: dikkop seems unhappy because of openssl stuff (FreeBSD 14-BETA1)

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-09-18T23:45:52Z
Lists: pgsql-hackers 
On Mon, Sep 18, 2023 at 03:11:27PM +0200, Tomas Vondra wrote:
> Both 11 and 12 failed with a weird openssl segfaults in plpython tests,
> see [2] and [3]. And 13 is stuck in some openssl stuff in plpython
> tests, with 100% CPU usage (for ~30h now):
> 
> #0  0x00000000850e86c0 in OPENSSL_sk_insert ()
>     from /usr/local/lib/libcrypto.so.11
> #1  0x00000000850a5848 in CRYPTO_set_ex_data ()
>     from /usr/local/lib/libcrypto.so.11
> ...
> 
> Full backtrace attached. I'm not sure what could possibly be causing
> this, except maybe something in FreeBSD? Or maybe there's some confusion
> about libraries? No idea.

FWIW, I've seen such corrupted and time-sensitive stacks in the past
in the plpython tests in builds when python linked to a SSL library
different than what's linked with the backend.  So that smells like a
packaging issue to me.
--
Michael

Commits

  1. Remove environment sensitivity in pl/tcl regression test.