Re: BUG #15226: (Changes in) LIBPQ prevents proper error captures andcrash client programs instead - Mailing list pgsql-bugs

From Jeff Janes
Subject Re: BUG #15226: (Changes in) LIBPQ prevents proper error captures andcrash client programs instead
Date
Msg-id CAMkU=1wSWtubyMYiJ7+1s9OfS79Hg=NWXc==MNBsB=qpdUtdFA@mail.gmail.com
Whole thread Raw
In response to BUG #15226: (Changes in) LIBPQ prevents proper error captures andcrash client programs instead  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Sun, Jun 3, 2018 at 8:03 AM, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      15226
Logged by:          Lance Zhang
Email address:      lance.zhang@gmail.com
PostgreSQL version: 10.4
Operating system:   Windows 10
Description:       

This mimimal test program will not run properly if the SQL supplied is
illegal. It crashes inside libqp. No chance is offered to client program to
detect and correct the error with facilities like PQerrorMessage(...).


Works for me.  What is your build chain and compilation command line?  How did you install PostgreSQL?

Cheers,

Jeff

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15226: (Changes in) LIBPQ prevents proper error captures andcrash client programs instead
Next
From: Ádám Maracska
Date:
Subject: Crashed libpq.dll in a multithreaded environment in case of SSLconnection + callstack