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

From Tom Lane
Subject Re: Preventing abort() and exit() calls in libpq
Date
Msg-id 523290.1625021963@sss.pgh.pa.us
Whole thread Raw
In response to Re: Preventing abort() and exit() calls in libpq  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Preventing abort() and exit() calls in libpq  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Yura Sokolov
Date:
Subject: Re: Extensible storage manager API - smgr hooks
Next
From: Noah Misch
Date:
Subject: Re: What is "wraparound failure", really?