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: "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>, "alvherre(at)alvh(dot)no-ip(dot)org" <alvherre(at)alvh(dot)no-ip(dot)org>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz>
Subject: Re: Preventing abort() and exit() calls in libpq
Date: 2021-07-02 22:45:21
Message-ID: 1187406.1625265921@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jacob Champion <pchampion(at)vmware(dot)com> writes:
> On Fri, 2021-07-02 at 18:20 -0400, Tom Lane wrote:
>> What configure options are you using?

> Just `./configure --enable-coverage`, nothing else. I distclean'd right
> before for good measure.

Hmph. There's *something* different about your setup from what
either Alvaro or I tried. What's the compiler (and version)?
What's the platform exactly?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2021-07-02 22:51:55 Re: Preventing abort() and exit() calls in libpq
Previous Message Jacob Champion 2021-07-02 22:38:10 Re: Preventing abort() and exit() calls in libpq