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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jacob Champion <pchampion(at)vmware(dot)com>
Cc: "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(dot)org>, "daniel(at)yesql(dot)se" <daniel(at)yesql(dot)se>, "info(at)cspug(dot)cz" <info(at)cspug(dot)cz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>
Subject: Re: Preventing abort() and exit() calls in libpq
Date: 2021-07-03 15:23:56
Message-ID: 1242586.1625325836@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> Hmmm ... mine is 8.4.1.
> I'm about to go out to dinner, but will check into this with some
> newer gcc versions later.

Tried --enable-coverage on Fedora 34 (with gcc 11.1.1) and sure
enough there's an exit() call being inserted. I've pushed a fix
to just disable the check altogether in --enable-coverage builds.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2021-07-03 15:26:00 Re: rand48 replacement
Previous Message Peter Eisentraut 2021-07-03 15:00:42 Re: OpenSSL 3.0.0 compatibility