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

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: Preventing abort() and exit() calls in libpq
Дата
Msg-id alpine.DEB.2.22.394.2106281013430.1401908@pseudo
обсуждение исходный текст
Ответ на Re: Preventing abort() and exit() calls in libpq  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Preventing abort() and exit() calls in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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 по дате отправления:

Предыдущее
От: Fabien COELHO
Дата:
Сообщение: Re: Overflow hazard in pgbench
Следующее
От: Anna Akenteva
Дата:
Сообщение: Re: Write visibility map during CLUSTER/VACUUM FULL