Re: ODBC Driver crash with MS Access 2007 (from GENERAL)

Hi

I'm currently encountering an interesting issue with the PostgreSQL ODBC
driver on Windows. I'm unlucky enough to have to use MS Access 2007 for
a project at the moment, with PostgreSQL providing the storage through
ODBC. It all works as well as can be expected from Access, except that
MS Access crashes when it quits.

The crash only occurs when the PostgreSQL ODBC driver has been used. If
the Access database file is opened but only Access-internal tables are
operated on, there's no crash when Access quits.

The crash occurs whether a file, system, or user DSN is being used.
I can reproduce this on two different machines. It happens with or
without SSL in use. It affects any Access 2007 database with a
PostgreSQL ODBC connection in use, including a newly created blank
database with a freshly linked table.

Because Windows is full of stripped binaries and limited debugging tools
I'm not able to get anything as useful as a backtrace at the moment.
I've had a quick look and strangely the crash address doesn't seem to be
part of the address space mapped to any DLLs. Windows Crash Reporter
seems to agree, in that it indicates that the module name is "unknown".

I'm at a bit of a loss. I'm used to debugging problems on platforms with
luxuries like symbol names in binaries, or at least my own code on
win32 where I can build it for debugging.

Anybody else seeing, or seen, similar issues?

--
Craig Ringer

Hi Craig,
Which version of psqlodbc driver are you using ?

Craig Ringer wrote:
> Hi
>
> I'm currently encountering an interesting issue with the PostgreSQL ODBC
> driver on Windows. I'm unlucky enough to have to use MS Access 2007 for
> a project at the moment, with PostgreSQL providing the storage through
> ODBC. It all works as well as can be expected from Access, except that
> MS Access crashes when it quits.
>
> The crash only occurs when the PostgreSQL ODBC driver has been used. If
> the Access database file is opened but only Access-internal tables are
> operated on, there's no crash when Access quits.
>
> The crash occurs whether a file, system, or user DSN is being used.
> I can reproduce this on two different machines.

Could you send me directly the Mylog output ?

regards,
Hiroshi Inoue

> It happens with or
> without SSL in use. It affects any Access 2007 database with a
> PostgreSQL ODBC connection in use, including a newly created blank
> database with a freshly linked table.
>
> Because Windows is full of stripped binaries and limited debugging tools
> I'm not able to get anything as useful as a backtrace at the moment.
> I've had a quick look and strangely the crash address doesn't seem to be
> part of the address space mapped to any DLLs. Windows Crash Reporter
> seems to agree, in that it indicates that the module name is "unknown".
>
> I'm at a bit of a loss. I'm used to debugging problems on platforms with
> luxuries like symbol names in binaries, or at least my own code on
> win32 where I can build it for debugging.
>
> Anybody else seeing, or seen, similar issues?
>
> --
> Craig Ringer

Hiroshi Inoue wrote:
> Hi Craig,
> Which version of psqlodbc driver are you using ?

That would've been clever to provide, yes. Especially given how I
grumble when people fail to provide such details.

The psqlODBC driver version is 8.3.3.0 (containing libpq 8.3.4.8263).

Both systems are XP SP3 hosts running fully patched Access 2007. Both
are connecting to a PostgreSQL 8.3.3 server running on a Linux host. One
is on real physical hardware that's otherwise been utterly reliable; the
other is a kvm virtual machine that's similarly solid.

Interestingly, I didn't observe this issue when connecting to a server
running locally on the Window dev machine that hosts Access during
earlier development. It was only once I switched to a DSN pointing to a
remote server running on a Linux machine that issues arose.

I'll send you the mylog output off-list shortly.

--
Craig Ringer

Hiroshi Inoue wrote:

> Craig Ringer wrote:
>> Hi
>>
>> I'm currently encountering an interesting issue with the PostgreSQL ODBC
>> driver on Windows. I'm unlucky enough to have to use MS Access 2007 for
>> a project at the moment, with PostgreSQL providing the storage through
>> ODBC. It all works as well as can be expected from Access, except that
>> MS Access crashes when it quits.
>>
>> The crash only occurs when the PostgreSQL ODBC driver has been used. If
>> the Access database file is opened but only Access-internal tables are
>> operated on, there's no crash when Access quits.
>>
>> The crash occurs whether a file, system, or user DSN is being used.
>> I can reproduce this on two different machines.
>
> Could you send me directly the Mylog output ?

Sorry it's taken so long to respond - phone system meltdowns and other
fun took priority. I've attached the mylog output, and it looks like it
might well be crashing during disconnect.

Ideas?

--
Craig Ringer

Craig Ringer wrote:
> Hiroshi Inoue wrote:

>> Could you send me directly the Mylog output ?

Whoops. Sorry, list, that was ... silly.

--
Craig Ringer