Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOIYb-0001Js-Jl for pgsql-bugs@arkaria.postgresql.org; Sun, 27 Feb 2022 12:21:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nOIY4-0003uj-UE for pgsql-bugs@arkaria.postgresql.org; Sun, 27 Feb 2022 12:21:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOIY4-0003ua-Ln for pgsql-bugs@lists.postgresql.org; Sun, 27 Feb 2022 12:21:12 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nOIXz-0008Nx-Tt for pgsql-bugs@lists.postgresql.org; Sun, 27 Feb 2022 12:21:11 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 9A5773200AF3; Sun, 27 Feb 2022 07:21:06 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 27 Feb 2022 07:21:06 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=O4YlWMFHPg/XQrrT5IqNYeDpyXsVdfVofEI3Pp krP+Y=; b=e+yeGeyd4zyI0XUkICis3d5lyzb/FTxa/RVCiOsnUX1FkbTgY+RZA7 1tbPbJFrpJPhvujIKYmgViwuyOQ3eaE9t4st4q/XqbPHzgepFPdEvLjx3KsEK9DW NGYxiUKrmOOYBZ35P4iazthub5LGn2bzSO+NrKPZ0We81zJUMTFQiOOWmuforQaT iZkYWVZTc/EL5AW20g/y47r/x4VyF/Z7OVIAFqjZ52cD6csIYj8NzEw9AoLWCpBs MAXviRf1qn3V5d0izEmZK74PDliW+XnGIYX1+ktZ/OOiQVmW1NCTdVacIOD3OaRq z8CmAghvzXDsgnShRNuFDYpalh8gAcfA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=O4YlWMFHPg/XQrrT5 IqNYeDpyXsVdfVofEI3PpkrP+Y=; b=jmyTyPoT9LTTn5pqmY4YNF06teBXqJBQD J8ocsHXZNso2CdnNSFfYkYTjfuU+DbJFjKYiz/xo0PBvyWBuocOKGVUnv44U6lKs HRYTlHTZ5usexdXzTXTW2913hErYuWJ5hviE79E7jH/reHcTZ/QzLxNGi3vqzqW/ QHpSjAQG4yl1XP1Q4N+qnfHbjkyH1my9uZk7SXKAf+8U/oRrLrwods6/STp3EPUS ueACf23alzFrUUPmFCFWRhaVp3sKfKz4BCI8j5irAMcpOaYmdPgOtpmPATfLLp+Y +RriIn+RMU+1JZ05gIwQk8DlxKb9rYuwwduBKVOO0gfnR6Lh2MxJA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrleekgdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecufghrlhcuvffnffculdejtddmnecujfgurhepfffhvf fukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhi vghruceomhhitghhrggvlhesphgrqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnh epvdegudeuhfdtueeltedtveejheehieevueeigeelteegleejleeiueeiheegvefhnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepmhhitghhrg gvlhesphgrqhhuihgvrhdrgiihii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 27 Feb 2022 07:21:04 -0500 (EST) Date: Sun, 27 Feb 2022 21:20:57 +0900 From: Michael Paquier To: 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 Message-ID: References: <17421-790ff887e3188874@postgresql.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="H3Ok9sGPmUAT1uWZ" Content-Disposition: inline In-Reply-To: <17421-790ff887e3188874@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --H3Ok9sGPmUAT1uWZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=3D0x9fb73f0, ctxnum=3D0, > -------- >=20 > 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 --H3Ok9sGPmUAT1uWZ Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmIbbKkACgkQnvQgOdby QH34DA/8DbVgkLvpFV0XZhZbimhIVy2aF/lLhL1vaSN8Dm8Ex2hAQFb6BH8KKSaw A6k9f36xTjbM2Ghdiv4Q5+KrF65uE9eLTsVqJI1MiTt4hxzp6Bi+tv7cwG1h8jRW QsyCDGIzMJfviX4iEjWZwxWqnN09XF5QUbX5MD4vPgnAKp9mXJmjmaZuF/tbPWeH oN9OW3dINJaeetDYdyK9+ptH4iZvXfwsugDPxos1zUNH64LOH64i8KHH++AYXB2v H2n5EV+5j3gdPdwdWtRWOrdOPZnbv3AafAsx6mZAog7UALqvfXyBmWGmx5iYmy78 y7tpeLo2bPZEdy6qlo4atVf3fQ7aaash+4K1rGUyfFmn0wKkABJZyvOAWfipG+s9 LDQou2XZWC16dly92Sf1HY3OXUkVmr7ciz7TjzqrDlpvm+2IM8tZouhlUAOkXDCp 95SvvXEpeb2kCh0CA/w/F8esiPXvpClhCTjivq7NTwJeE0tKTVLu+XSyySmk4vbT UkR2O1wxJLCoGVqzGlmVE5VPNGECEMAwbYa9v5G70CWl9vqk/dXbiU61PDIF4cqD 7j9pI2a+Lrv8xRru0l50/JvOjosD+e2vAFW8Yjonhddyscj3MA+X1bknAd3N/cJV i/TVtzq1zxOnt6jW45xSh8YVFifXQPuT8JrDjwbIiVeuEYQmOtE= =Twgc -----END PGP SIGNATURE----- --H3Ok9sGPmUAT1uWZ--