Re: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8

On Sun, Feb 27, 2022 at 05:21:32AM +0000, PG Bug reporting form wrote:
> Have you ever seen this error?

No such issue has been reported AFAIK. If you really are on 12.1, you
may want to update to the latest version of 12.X and retry if the
error still shows up.

> --------
> (gdb) where
> #0 0xf7163dc7 in strlen () from /usr/lib/libc.so.6
> #1 0x08169faf in dopr ()
> #2 0x08169c19 in pg_vsnprintf ()
> #3 0x08169c6b in pg_snprintf ()
> #4 0x08153ec7 in ecpg_raise_backend ()
> #5 0x081540bb in ecpg_check_Pqresult ()
> #6 0x0814da6a in ecpg_autostart_transaction ()
> #7 0x0814ebc6 in ecpg_do ()
> #8 0x0814ec79 in ECPGdo ()
> #9 0xf7f96e40 in TJVvDatabaseAPI::_ExecSQL (this=0x9fb73f0, ctxnum=0,
> --------
>
> I am using the 32-bit client for RHEL8 and it calls PostgreSQL API, thus I
> encountered this error.

Hm. Could you isolate that in a self-contained test case? Based on
this trace, it looks like "message" is NULL, which may be possible
because pqInternalNotice() missed something? I would not bet on
errorMessage being NULL, but there may be holes..
--
Michael