MIME-Version: 1.0
References: <112f6883-34e4-4372-8bda-d04f45ee31bf@gmail.com>
In-Reply-To: <112f6883-34e4-4372-8bda-d04f45ee31bf@gmail.com>
From: Dave Cramer <davecramer@postgres.rocks>
Date: Mon, 26 Feb 2024 15:11:14 -0500
Message-ID: 
 <CADK3HHJLym2DzrBkrUbLysDE9K=-73g8XtxFpMKgdaWho0Jdew@mail.gmail.com>
Subject: Re: psqlodbc crashes while collecting diagnostic records with
 SQLGetDiagRecW
To: Andrey Sukhanov <siwenter@gmail.com>
Cc: pgsql-odbc@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000e93d7006124e835a"
Archived-At: 
 <https://www.postgresql.org/message-id/CADK3HHJLym2DzrBkrUbLysDE9K%3D-73g8XtxFpMKgdaWho0Jdew%40mail.gmail.com>
Precedence: bulk

--000000000000e93d7006124e835a
Content-Type: text/plain; charset="UTF-8"

Hi Andrey,

I've tried on PostgreSQL 11 and 15 with no luck to replicate this problem.

Is it possible for you to debug it and send more information?

Dave Cramer
www.postgres.rocks


On Thu, 22 Feb 2024 at 01:29, Andrey Sukhanov <siwenter@gmail.com> wrote:

> Dear pgsql-odbc developers,
>
> Windows 10,  psqlodbc 16 (psqlodbc35w.dll), postgresql 11.
> Getting certain amount of diagnostic records with SQLGetDiagRecW crashes
> the application with memory access violation.
>
> Steps to reproduce:
> 1. Create procedure:
> CREATE OR REPLACE PROCEDURE crashme()
> LANGUAGE plpgsql
> AS $$
> BEGIN
> FOR i IN 1..841 LOOP
>          RAISE NOTICE 'msgmsgmsgmsg (%)', i;
> END LOOP;
> END; $$;
>
> 2. Use example code in attachments.
> 3. Application crashes with memory access violation after calling
> SQLGetDiagRecW function, with iRecord = 332.
> Application doesn't crash if number of iterations in  procedure's for
> loop is changed.
> Expected outcome: SQLGetDiagRecW would return SQL_NO_DATA when there's
> no more diagnostic records.
>
> Regards,
> Andrey
>

--000000000000e93d7006124e835a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi=C2=A0Andrey,<div><br></div><div>I&#39;ve tried on Postg=
reSQL 11 and 15 with no luck to replicate this problem.</div><div><br></div=
><div>Is it possible for you to debug it and send more information?</div><d=
iv><br clear=3D"all"><div><div dir=3D"ltr" class=3D"gmail_signature" data-s=
martmail=3D"gmail_signature"><div dir=3D"ltr">Dave Cramer<div>www.postgres.=
rocks</div></div></div></div><br></div></div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 22 Feb 2024 at 01:29, Andrey=
 Sukhanov &lt;<a href=3D"mailto:siwenter@gmail.com">siwenter@gmail.com</a>&=
gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear =
pgsql-odbc developers,<br>
<br>
Windows 10,=C2=A0 psqlodbc 16 (psqlodbc35w.dll), postgresql 11.<br>
Getting certain amount of diagnostic records with SQLGetDiagRecW crashes <b=
r>
the application with memory access violation.<br>
<br>
Steps to reproduce:<br>
1. Create procedure:<br>
CREATE OR REPLACE PROCEDURE crashme()<br>
LANGUAGE plpgsql<br>
AS $$<br>
BEGIN<br>
FOR i IN 1..841 LOOP<br>
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 RAISE NOTICE &#39;msgmsgms=
gmsg (%)&#39;, i;<br>
END LOOP;<br>
END; $$;<br>
<br>
2. Use example code in attachments.<br>
3. Application crashes with memory access violation after calling <br>
SQLGetDiagRecW function, with iRecord =3D 332.<br>
Application doesn&#39;t crash if number of iterations in=C2=A0 procedure=
9;s for <br>
loop is changed.<br>
Expected outcome: SQLGetDiagRecW would return SQL_NO_DATA when there&#39;s =
<br>
no more diagnostic records.<br>
<br>
Regards,<br>
Andrey<br>
</blockquote></div>

--000000000000e93d7006124e835a--