Re: BUG #15226: (Changes in) LIBPQ prevents proper error captures and crash client programs instead

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: lance(dot)zhang(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15226: (Changes in) LIBPQ prevents proper error captures and crash client programs instead
Date: 2018-06-03 12:55:25
Message-ID: CAMkU=1wSWtubyMYiJ7+1s9OfS79Hg=NWXc==MNBsB=qpdUtdFA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Jun 3, 2018 at 8:03 AM, PG Bug reporting form <
noreply(at)postgresql(dot)org> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 15226
> Logged by: Lance Zhang
> Email address: lance(dot)zhang(at)gmail(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ádám Maracska 2018-06-03 18:14:59 Crashed libpq.dll in a multithreaded environment in case of SSL connection + callstack
Previous Message PG Bug reporting form 2018-06-03 12:03:51 BUG #15226: (Changes in) LIBPQ prevents proper error captures and crash client programs instead