Re: Preventing abort() and exit() calls in libpq

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>
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>, "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(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:38:10
Message-ID: 7a58bd2bcebeddc9b7ba7882ef0dbe693e04925a.camel@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 2021-07-02 at 18:20 -0400, Tom Lane wrote:
> What configure options are you using?

Just `./configure --enable-coverage`, nothing else. I distclean'd right
before for good measure.

> Does "nm -u" report "exit" being referenced from any *.o in libpq,
> or from any *_shlib.o in src/port/ or src/common/ ?

Only src/common:

controldata_utils_shlib.o:
U close
U __errno_location
U exit
...
fe_memutils_shlib.o:
U exit
...
file_utils_shlib.o:
U close
U closedir
U __errno_location
U exit
...
hex_shlib.o:
U exit
...
psprintf_shlib.o:
U __errno_location
U exit
...
stringinfo_shlib.o:
U __errno_location
U exit
...
username_shlib.o:
U __errno_location
U exit
...

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-07-02 22:45:21 Re: Preventing abort() and exit() calls in libpq
Previous Message Tom Lane 2021-07-02 22:20:25 Re: Preventing abort() and exit() calls in libpq