From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: hirose.masay-01@jp.fujitsu.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8
Date: Sun, 27 Feb 2022 11:30:58 -0500
Message-ID: <2360630.1645979458@sss.pgh.pa.us> (raw)
In-Reply-To: <YhtsqXFtjC86HdeM@paquier.xyz>
References: <17421-790ff887e3188874@postgresql.org>
<YhtsqXFtjC86HdeM@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> 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..
Yeah. It seems likely that this is a longstanding ecpglib bug
that was previously masked by platform snprintfs not crashing
on printf("%s", NULL). If so, it's masked again in 12.8 and
later (cf 3779ac62d), but it's still a bug in that ecpg won't
print anything useful when this edge condition --- whatever it
is --- happens. So, could we see a test case?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, hirose.masay-01@jp.fujitsu.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17421: Core dump in ECPGdo() when calling PostgreSQL API from 32-bit client for RHEL8
In-Reply-To: <2360630.1645979458@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox