From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Wolfgang Walther <walther(at)technowledgy(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Date: | 2024-03-16 20:19:34 |
Message-ID: | CA+hUKGJhp0opkCybdOrbQSMyHX8cRuLh2ygkqtivizCqK6kfOA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Sun, Mar 17, 2024 at 4:56 AM Wolfgang Walther
<walther(at)technowledgy(dot)de> wrote:
> Any ideas?
I'd look into whether there is a difference in the rules it uses for
deciding not to trust LD_LIBRARY_PATH, which seems to be around here
somewhere:
https://github.com/bminor/musl/blob/7ada6dde6f9dc6a2836c3d92c2f762d35fd229e0/ldso/dynlink.c#L1812
I wonder if you can break into an affected program and check out the
magic there. FWIW on MacOS something equivalent happens at the moment
we execute a shell, because the system shell is 'code signed' and that
OS treats signed stuff similar to setuid binaries for this purpose
(IIRC setting SHELL to point to a suitable unsigned shell could work
around the problem there?)
Another interesting thing that came up when I googled musl/glibc
differences -- old but looks plausibly still true (not that I expect
our code to be modifying that stuff in place, just something to
check):
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walther | 2024-03-16 20:21:55 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | Tom Lane | 2024-03-16 20:10:56 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
From | Date | Subject | |
---|---|---|---|
Next Message | Wolfgang Walther | 2024-03-16 20:21:55 | Re: Regression tests fail with musl libc because libpq.so can't be loaded |
Previous Message | David G. Johnston | 2024-03-16 20:17:14 | Re: REVOKE FROM warning on grantor |