Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <pchampion@vmware.com>
Cc: "daniel@yesql.se" <daniel@yesql.se>, "info@cspug.cz" <info@cspug.cz>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "alvherre@alvh.no-ip.org" <alvherre@alvh.no-ip.org>, "michael@paquier.xyz" <michael@paquier.xyz>
Date: 2021-07-02T22:45:21Z
Lists: pgsql-hackers 
Jacob Champion <pchampion@vmware.com> writes:
> 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.

Hmph.  There's *something* different about your setup from what
either Alvaro or I tried.  What's the compiler (and version)?
What's the platform exactly?

			regards, tom lane

Commits

  1. Further restrict the scope of no-exit()-in-libpq test.

  2. Improve build-time check that libpq doesn't call exit().

  3. Fix portability fallout from commit dc227eb82.

  4. Add a build-time check that libpq doesn't call exit() or abort().