| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jacob Champion <pchampion(at)vmware(dot)com> |
| Cc: | "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(dot)org>, "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:20:25 |
| Message-ID: | 1170291.1625264425@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jacob Champion <pchampion(at)vmware(dot)com> writes:
> 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
Hm, weird. I don't see that here on RHEL8, and
https://coverage.postgresql.org seems to be working so it doesn't fail on
Alvaro's Debian setup either. What configure options are you using?
Does "nm -u" report "exit" being referenced from any *.o in libpq,
or from any *_shlib.o in src/port/ or src/common/ ?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2021-07-02 22:38:10 | Re: Preventing abort() and exit() calls in libpq |
| Previous Message | Jacob Champion | 2021-07-02 22:15:45 | Re: Preventing abort() and exit() calls in libpq |