From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Brent Smith <brent(dot)smith(at)kepware(dot)com> |
Cc: | "pgsql-odbc(at)postgresql(dot)org" <pgsql-odbc(at)postgresql(dot)org>, "inoue(at)tpf(dot)co(dot)jp" <inoue(at)tpf(dot)co(dot)jp> |
Subject: | Re: Unknown exceptions possibly originating from psqlodbc |
Date: | 2015-06-15 08:25:49 |
Message-ID: | CAMsr+YFMsUtsPThZ8Pti3vGdXVMWWTbJ1XOH7-peNQUmDDSzbg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 29 April 2015 at 21:17, Brent Smith <brent(dot)smith(at)kepware(dot)com> wrote:
> My primary question is, do you have any insight into what exceptions you
> might throw in the case of a record set update? Further, are there any
> tools, header files, debug versions, logging utilities, etc. that you could
> provide to help us diagnose this problem?
I strongly recommend that you check out the psqlODBC sources from git
and do a debug build.
You should then set up the post-mortem debugger on the problem system
to generate minidumps, or to trap directly into Visual Studio if
practical. Alternately you can just attach VS to the problem process
(if it's just one) and wait for the problem to arise.
Using a debug build of the driver will make life a lot easier.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Hellegers | 2015-06-15 18:27:27 | Compiling without libpq |
Previous Message | Craig Ringer | 2015-06-15 08:17:27 | Minor fixes to Windows tests |