From: | Jacob Champion <pchampion(at)vmware(dot)com> |
---|---|
To: | "tgl(at)sss(dot)pgh(dot)pa(dot)us" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | "daniel(at)yesql(dot)se" <daniel(at)yesql(dot)se>, "info(at)cspug(dot)cz" <info(at)cspug(dot)cz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz> |
Subject: | Re: Preventing abort() and exit() calls in libpq |
Date: | 2021-07-02 22:15:45 |
Message-ID: | 647ee70e51621c8f35c8c06d20faf8c96345e6d0.camel@vmware.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 2021-06-30 at 10:42 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > On 2021-Jun-30, Tom Lane wrote:
> > > You mentioned __gcov_exit, but I'm not sure if we need an
> > > exception for that. I see it referenced by the individual .o
> > > files, but the completed .so has no such reference, so at least
> > > on RHEL8 it's apparently satisfied during .so linkage. Do you
> > > see something different?
> > Well, not really. I saw it but only after I removed -fprofile-arcs from
> > Makefile.shlib's link line; but per my other email, that doesn't really
> > work.
> > Everything seems to work well for me after removing abort from that grep.
>
> OK, thanks, will push a fix momentarily.
With latest HEAD, building with --enable-coverage still fails on my
Ubuntu 20.04:
! nm -A -u libpq.so.5.15 2>/dev/null | grep -v __cxa_atexit | grep exit
libpq.so.5.15: U exit@@GLIBC_2.2.5
I don't see any exit references in the libpq objects or in
libpgport_shlib, so it seems like libpgcommon_shlib is the culprit... I
assume turning off optimizations leads to less dead code elimination?
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-07-02 22:20:25 | Re: Preventing abort() and exit() calls in libpq |
Previous Message | Fabien COELHO | 2021-07-02 21:51:42 | Re: rand48 replacement |