[Bug 56786] New: Proprietary native ODBC driver crashing

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=56786

Bug ID: 56786
           Summary: Proprietary native ODBC driver crashing
           Product: Wine-staging
           Version: 9.10
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail]
      Distribution: ---

Created attachment 76592
  --> https://bugs.winehq.org/attachment.cgi?id=76592
Backtrace of failing call

(Using wine-9.10 (Staging) as I believe staging id required for native odbc)

.Net app to retrieve data via odbc using a proprietary native 64 bit odbc
driver fails with System.AccessViolationException 'Attempted to read or write
protected memory' when interop is calling 'SQLDriverConnectW'

Tried c++ to remove .Net from the equation and depending on what connection
string is used it yields a different error. If connection details are passed in
the connectionstring ie:
   Driver=xxxxx ODBC
driver;Server=x.x.x.x,yyy;DBNAME=xxxxx;UID=xxxxx;PWD=xxxxx;
The following error occurs:
   Error in SQLDriverConnect(hDbc, GetDesktopWindow(), pwszConnStr, SQL_NTS,
NULL, 0, NULL, SQL_DRIVER_COMPLETE)
   0024:fixme:odbc:SQLFreeHandle (HandleType 2, Handle 00000000006F3DA0)
   0024:fixme:odbc:SQLFreeHandle (HandleType 1, Handle 00000000006F3D70)

A backtrace is not given and even when launching via 'wine winedbg ...',
setting $BreakOnFirstChance=0 and 'cont'inuing I do not get one.

If I pass a DSN in the connection string of a data source preconfigured in the
registry (exported from working windows machine and imported):
    DSN=xxxxx;UID=xxxxx;PWD=xxxxx
A backtrace is produced (attached, albeit with failing dll renamed to xodbc64).
I can supply the driver privately on request.