From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Michael Paquier <michael@paquier.xyz>,
        Jacob Champion <pchampion@vmware.com>,
        "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
        Daniel Gustafsson <daniel@yesql.se>, info@cspug.cz
Subject: Re: Preventing abort() and exit() calls in libpq
In-reply-to: <202106292357.fdr5qq2i7725@alvherre.pgsql>
References: <202106292357.fdr5qq2i7725@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Tue, 29 Jun 2021 19:57:05 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <523289.1625021963.1@sss.pgh.pa.us>
Date: Tue, 29 Jun 2021 22:59:23 -0400
Message-ID: <523290.1625021963@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/523290.1625021963%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Ah, I nm'd all files in src/interfaces/libpq and got no hits for abort.
> But I did get one in libpgport_shlib.a:

> path_shlib.o:
>                  U abort

Yeah, there is one in get_progname().  But path.o shouldn't be getting
pulled into libpq ... else why aren't all the animals failing?

What platform does the coverage report run on exactly?

			regards, tom lane