Hi all,
Sorry to disturb if this is out of place. I am using DBD-ODBC-0.28,
which appears to be the latest version of this module from CPAN. I was
running with trace level 4 and suffered a core dump. The problem seems
to be fixed by the following change to dbdimp.c. Sorry for the
formatting, it is my sorry attempt at cut and paste.
*** /usr/tmp/DBD-ODBC-0.28/dbdimp.c Thu Mar 23 06:23:55 2000
--- dbdimp.c Fri Oct 5 19:43:22 2001
***************
*** 195,205 ****
rc=SQLError(imp_dbh->henv, imp_dbh->hdbc, 0,
sqlstate, &NativeError,
ErrorMsg, sizeof(ErrorMsg)-1, &ErrorMsgLen);
if (rc == SQL_SUCCESS || rc == SQL_SUCCESS_WITH_INFO)
! fprintf(DBILOGFP, "SQLDriverConnect failed: %s %s\n", sqlstate,
ErrorMsgLen);
}
#endif /* DriverConnect supported */
if (DBIS->debug >= 2)
fprintf(DBILOGFP, "SQLConnect '%s', '%s', '%s'\n", dbname, uid,
pwd);
--- 195,205 ----
rc=SQLError(imp_dbh->henv, imp_dbh->hdbc, 0,
sqlstate, &NativeError,
ErrorMsg, sizeof(ErrorMsg)-1, &ErrorMsgLen);
if (rc == SQL_SUCCESS || rc == SQL_SUCCESS_WITH_INFO)
! fprintf(DBILOGFP, "SQLDriverConnect failed: %s %*s\n", sqlstate,
ErrorMsgLen, ErrorMsg);
}
#endif /* DriverConnect supported */
if (DBIS->debug >= 2)
fprintf(DBILOGFP, "SQLConnect '%s', '%s', '%s'\n", dbname, uid,
pwd);
It seems to work fine with the change.
Hope this helps,
Ian
