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

From Fabien COELHO
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id alpine.DEB.2.22.394.2106281013430.1401908@pseudo
Whole thread Raw
In response to Re: Preventing abort() and exit() calls in libpq  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Preventing abort() and exit() calls in libpq
List pgsql-hackers
>> +# 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.

A possible trick is to add ccp flags such as: -Dexit=exit_BAD 
-Dabort=abort_BAD.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Overflow hazard in pgbench
Next
From: Anna Akenteva
Date:
Subject: Re: Write visibility map during CLUSTER/VACUUM FULL