RE: windows AppVerifier reports memory leak after strdup (psqlodbc35w.dll ver 13.00) - Mailing list pgsql-odbc

From Першин Юрий Петрович
Subject RE: windows AppVerifier reports memory leak after strdup (psqlodbc35w.dll ver 13.00)
Date
Msg-id 194f365f33f640fd9397c4608819e06f@prosoftsystems.ru
Whole thread Raw
In response to windows AppVerifier reports memory leak after strdup (psqlodbc35w.dll ver 13.00)  (Першин Юрий Петрович <pershin@prosoftsystems.ru>)
List pgsql-odbc

Steps to reproduce subj:

1. Add wscript.exe to AppVerifier with Basics.Leak check

2. Create file pg_leak.vbs with the following code (replace YOUR_CONNECTION_STRING with yours):
Set c = CreateObject("ADODB.Connection")

c.Open "YOUR_CONNECTION_STRING"

Set cmd = CreateObject("ADODB.Command")

Set cmd.ActiveConnection = c

cmd.ActiveConnection.CursorLocation = 3 'clUseClient

cmd.CommandText = "SELECT COUNT(*) FROM INFORMATION_SCHEMA.TABLES"

cmd.CommandType = 1 'adCmdText

Set r = CreateObject("ADODB.Recordset")

r.Open cmd, , 1, 3, 1 'ctKeySet, ltOptimistic, adCmdText

MsgBox r.Fields(0).Value
3. Execute wscript.exe pg_leak.vbs
4. Launch AppVerifier.exe and see if it was happy with last wscript.exe session (was not happy)

5. Comment out line about CursorLocation and repeat steps 3-4. You should see the subj just disappeared.

 

pgsql-odbc by date:

Previous
From: Першин Юрий Петрович
Date:
Subject: windows AppVerifier reports memory leak after strdup (psqlodbc35w.dll ver 13.00)
Next
From: Першин Юрий Петрович
Date:
Subject: READ AV Bug@psqlodbc30a.dll