public inbox for [email protected]  
help / color / mirror / Atom feed
From: Dave Cramer <[email protected]>
To: Andrey Sukhanov <[email protected]>
Cc: [email protected]
Subject: Re: psqlodbc crashes while collecting diagnostic records with SQLGetDiagRecW
Date: Mon, 26 Feb 2024 15:11:14 -0500
Message-ID: <CADK3HHJLym2DzrBkrUbLysDE9K=-73g8XtxFpMKgdaWho0Jdew@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

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 <[email protected]> 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
>


view thread (6+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: psqlodbc crashes while collecting diagnostic records with SQLGetDiagRecW
  In-Reply-To: <CADK3HHJLym2DzrBkrUbLysDE9K=-73g8XtxFpMKgdaWho0Jdew@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox