Обсуждение: BUG #16787: ODBC driver (libpq.dll, psqlodbc30a.dll, psqlodbc30w.dll) issues

Поиск
Список
Период
Сортировка

BUG #16787: ODBC driver (libpq.dll, psqlodbc30a.dll, psqlodbc30w.dll) issues

От
PG Bug reporting form
Дата:
The following bug has been logged on the website:

Bug reference:      16787
Logged by:          Юрий Першин
Email address:      pershin@prosoftsystems.ru
PostgreSQL version: 13.1
Operating system:   Windows
Description:

Tried another mailing lists with no success.

1. Memory leak in psqlodbc30*.dll - probably missing
QR_Destructor(self->parsed) function call inside SC_Destructor(). Steps for
reproduce:
https://www.postgresql.org/message-id/194f365f33f640fd9397c4608819e06f%40prosoftsystems.ru
2. READ AV in psqlodbc30a.dll - you should remove strlen from strncpy_null
https://www.postgresql.org/message-id/15b7ea3bfae04c7992c6fcc1aaf8a3e5%40prosoftsystems.ru
3. Memory leak in libpq.dll - leaked 0x18 bytes
https://www.postgresql.org/message-id/2078341cd30141fbb8a54b7d63faca47%40prosoftsystems.ru
4. Underflow in psqlodbc30*.dll - when SQLNativeSqlW called with both
szSqlStr and cbSqlStrMax==0, { CONN_NO_MEMORY_ERROR, "Could not allocate
memory for output buffer" } raised by mistake


Re: BUG #16787: ODBC driver (libpq.dll, psqlodbc30a.dll, psqlodbc30w.dll) issues

От
Bruce Momjian
Дата:
On Tue, Dec 22, 2020 at 02:11:09AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      16787
> Logged by:          Юрий Першин
> Email address:      pershin@prosoftsystems.ru
> PostgreSQL version: 13.1
> Operating system:   Windows
> Description:        
> 
> Tried another mailing lists with no success.
> 
> 1. Memory leak in psqlodbc30*.dll - probably missing
> QR_Destructor(self->parsed) function call inside SC_Destructor(). Steps for
> reproduce:
> https://www.postgresql.org/message-id/194f365f33f640fd9397c4608819e06f%40prosoftsystems.ru
> 2. READ AV in psqlodbc30a.dll - you should remove strlen from strncpy_null
> https://www.postgresql.org/message-id/15b7ea3bfae04c7992c6fcc1aaf8a3e5%40prosoftsystems.ru
> 3. Memory leak in libpq.dll - leaked 0x18 bytes
> https://www.postgresql.org/message-id/2078341cd30141fbb8a54b7d63faca47%40prosoftsystems.ru
> 4. Underflow in psqlodbc30*.dll - when SQLNativeSqlW called with both
> szSqlStr and cbSqlStrMax==0, { CONN_NO_MEMORY_ERROR, "Could not allocate
> memory for output buffer" } raised by mistake

You would report ODBC issues here:

    pgsql-odbc@postgresql.org

    https://odbc.postgresql.org/faq.html#1.6

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee




RE: BUG #16787: ODBC driver (libpq.dll, psqlodbc30a.dll, psqlodbc30w.dll) issues

От
Першин Юрий Петрович
Дата:
Hi!

Item 3, leak static object in libpq.dll - fix at least, please (we use AppVerifier to make our software certified by
Microsoft)

pgsql-odbc: items 1-2 already there, not answered yet; item 4 - added
https://www.postgresql.org/message-id/231fbd20e4a0489aa814dd1b12f52ae2%40prosoftsystems.ru.

-----Original Message-----
From: Bruce Momjian [mailto:bruce@momjian.us] 
Sent: Tuesday, December 22, 2020 8:41 PM
To: Першин Юрий Петрович; pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16787: ODBC driver (libpq.dll, psqlodbc30a.dll, psqlodbc30w.dll) issues

On Tue, Dec 22, 2020 at 02:11:09AM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      16787
> Logged by:          Юрий Першин
> Email address:      pershin@prosoftsystems.ru
> PostgreSQL version: 13.1
> Operating system:   Windows
> Description:        
> 
> Tried another mailing lists with no success.
> 
> 1. Memory leak in psqlodbc30*.dll - probably missing
> QR_Destructor(self->parsed) function call inside SC_Destructor(). 
> Steps for
> reproduce:
> https://www.postgresql.org/message-id/194f365f33f640fd9397c4608819e06f
> %40prosoftsystems.ru 2. READ AV in psqlodbc30a.dll - you should remove 
> strlen from strncpy_null 
> https://www.postgresql.org/message-id/15b7ea3bfae04c7992c6fcc1aaf8a3e5
> %40prosoftsystems.ru 3. Memory leak in libpq.dll - leaked 0x18 bytes 
> https://www.postgresql.org/message-id/2078341cd30141fbb8a54b7d63faca47
> %40prosoftsystems.ru 4. Underflow in psqlodbc30*.dll - when 
> SQLNativeSqlW called with both szSqlStr and cbSqlStrMax==0, { 
> CONN_NO_MEMORY_ERROR, "Could not allocate memory for output buffer" } 
> raised by mistake

You would report ODBC issues here:

    pgsql-odbc@postgresql.org

    https://odbc.postgresql.org/faq.html#1.6

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee