Request a Demo
Home   >   mailing lists

Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL
Date
Msg-id 3007317.1765210195@sss.pgh.pa.us
Whole thread Raw
In response to [BUG] CRASH: ECPGprepared_statement() and ECPGdeallocate_all() when connection is NULL  (Shruthi Gowda <gowdashru@gmail.com>)
List pgsql-hackers
Tree view 
Shruthi Gowda <gowdashru@gmail.com> writes:
> The ECPG application crashes with a segmentation fault when calling
> specific deallocation or prepared statement functions without an
> established database connection. This is caused by a missing NULL check on
> the connection handle before attempting to access it.

Hmm ... poking around, I see several other places that aren't checking
the result of ecpg_get_connection.  Shouldn't we tighten them all?

            regards, tom lane

pgsql-hackers by date:

Previous
From: Bryan Green
Date:
Subject: Re: [PATCH] Allow complex data for GUC extra.
Next
From: "Vitaly Davydov"
Date:
Subject: RE: Newly created replication slot may be invalidated by checkpoint