Re: Preventing abort() and exit() calls in libpq - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id 7a58bd2bcebeddc9b7ba7882ef0dbe693e04925a.camel@vmware.com
Whole thread Raw
In response to Re: Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Preventing abort() and exit() calls in libpq  ("alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org>)
List 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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Preventing abort() and exit() calls in libpq
Next
From: Tom Lane
Date:
Subject: Re: Preventing abort() and exit() calls in libpq