Thread: Crash in CC_from_PGresult
Our customers are crashing on Windows in CC_from_PGresult up to version 10.2.0 of the 64-bit driver. Do you know if this crash is fixed in a later version? Or what can I do to help get it fixed?
The call stack in 10.2.0 is:
psqlodbc35w!CC_from_PGresult+0xb1
psqlodbc35w!CC_send_query_append+0x1081
psqlodbc35w!QR_next_tuple+0xc7e
psqlodbc35w!SC_fetch+0x16d
psqlodbc35w!PGAPI_ExtendedFetch+0x100d
psqlodbc35w!SQLFetch+0xe9
odbc32!SQLFetch+0x35a
Thanks,
Dan
Could you take Mylog output of the case?
regards,
Hiroshi Inoue
Our customers are crashing on Windows in CC_from_PGresult up to version 10.2.0 of the 64-bit driver. Do you know if this crash is fixed in a later version? Or what can I do to help get it fixed?
The call stack in 10.2.0 is:
psqlodbc35w!CC_from_PGresult+0xb1
psqlodbc35w!CC_send_query_append+0x1081
psqlodbc35w!QR_next_tuple+0xc7e
psqlodbc35w!SC_fetch+0x16d
psqlodbc35w!PGAPI_ExtendedFetch+0x100d
psqlodbc35w!SQLFetch+0xe9
odbc32!SQLFetch+0x35a
Thanks, Dan
All I have now is the dmp file from our crash dump reporting system.
I can try to find one of our customers and see if they can reproduce it to generate additional logs, but I don’t know how successful that will be. Do you have any ideas from the stack what might be going wrong so I can narrow down the possible repro steps?
Dan
From: Inoue, Hiroshi <h-inoue@dream.email.ne.jp>
Sent: Monday, July 23, 2018 3:50 PM
To: Daniel Cory <dcory@tableau.com>
Cc: pgsql-odbc@postgresql.org
Subject: Re: Crash in CC_from_PGresult
Hi Daniel,
Could you take Mylog output of the case?
regards,
Hiroshi Inoue
On 2018/07/24 1:32, Daniel Cory wrote:
Our customers are crashing on Windows in CC_from_PGresult up to version 10.2.0 of the 64-bit driver. Do you know if this crash is fixed in a later version? Or what can I do to help get it fixed?
The call stack in 10.2.0 is:
psqlodbc35w!CC_from_PGresult+0xb1
psqlodbc35w!CC_send_query_append+0x1081
psqlodbc35w!QR_next_tuple+0xc7e
psqlodbc35w!SC_fetch+0x16d
psqlodbc35w!PGAPI_ExtendedFetch+0x100d
psqlodbc35w!SQLFetch+0xe9
odbc32!SQLFetch+0x35a
Thanks,
Dan