| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se>, info(at)cspug(dot)cz |
| Subject: | Re: Preventing abort() and exit() calls in libpq |
| Date: | 2021-06-29 23:46:35 |
| Message-ID: | 202106292346.oggetdriqizn@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jun-29, Tom Lane wrote:
> More troublingly, fossa reports this:
>
> ! nm -A -g -u libpq.so.5.15 2>/dev/null | grep -v '_eprintf\\.o:' | grep -e abort -e exit
> libpq.so.5.15: U abort@@GLIBC_2.2.5
>
> Where is that coming from? hippopotamus and jay, which seem to
> be different compilers on the same physical machine, aren't showing
> it. That'd lead to the conclusion that icc is injecting abort()
> calls of its own accord, which seems quite nasty. Lacking an icc
> license, I can't poke into that more directly here.
I noticed that the coverage report is not updating, and lo and behold
it's failing this bit.
I can inspect the built files ... what exactly are you looking for?
--
Álvaro Herrera Valdivia, Chile
<Schwern> It does it in a really, really complicated way
<crab> why does it need to be complicated?
<Schwern> Because it's MakeMaker.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-06-29 23:57:05 | Re: Preventing abort() and exit() calls in libpq |
| Previous Message | Josef Šimánek | 2021-06-29 23:43:15 | Re: [PATCH] Don't block HOT update by BRIN index |