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

From Michael Paquier
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id YNl/rGAtp0Ovmtis@paquier.xyz
Whole thread Raw
In response to Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Preventing abort() and exit() calls in libpq
Re: Preventing abort() and exit() calls in libpq
List pgsql-hackers
On Sat, Jun 26, 2021 at 05:29:29PM -0400, Tom Lane wrote:
> I'll stick this into the CF list to see if the cfbot agrees that
> it finds the abort() problems...

The CF Bot is finding those problems.

> +# Check for functions that libpq must not call.
> +# (If nm doesn't exist or doesn't work on shlibs, this test will silently
> +# do nothing, which is fine.)
> +.PHONY: check-libpq-refs
> +check-libpq-refs: $(shlib)
> +    @! nm -A -g -u $< 2>/dev/null | grep -e abort -e exit

"abort" and "exit" could be generic terms present in some other
libraries.  Could be be better to match with "U abort" and "U exit"
instead?  MinGW has a nm command, and it has a compatible option set,
so I think that it should work.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Different compression methods for FPI
Next
From: Michael Paquier
Date:
Subject: Re: Different compression methods for FPI