Bug #5255 Driver trace generation (Debug mode option 4) is broken in 3.51.09
Submitted: 27 Aug 2004 15:22 Modified: 9 Oct 2005 11:20
Reporter: Armin Schöffmann (OCA) Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / ODBC Severity:S2 (Serious)
Version:3.51.09 OS:Windows (WIN XP PRO SP2 DE)
Assigned to: CPU Architecture:Any

[27 Aug 2004 15:22] Armin Schöffmann
Description:
debug flag '4' has no effect anymore.
no myodbc.log is created in c:\

flag 524288 (query-log generation) is not affected

there might be other issues also, as my app is currently not working with the new driver release. without the debug-trace-feature it's hard to figure out the cause...

How to repeat:
switch to myodbc3d.dll
create a new odbc-connection with all debug-flags enabled or
use the corresponding odbc-api-calls
[12 Apr 2005 2:25] Peter Harvey
By default the driver is built with DBUG_OFF and this prevents init_dbug_log() from being called. One needs to build a debug version of the driver and then turn on the debugging.
[6 Oct 2005 21:42] Mark Matthews
Please reverify w/ 3.51.12 as there are fixes in there that most likely address this bug.
[9 Oct 2005 11:20] Vasily Kishkin
It's re-verified on 3.51.12. I built myodbc sources with DBUG_ON. myodbc.log was created c:\.