[Mono-dev] Strange ODBC/ComponentModel problem

[Ernesto]

Hi,

I'm having this weird ODBC problem. I didn't file a bug report because I 
don't know how to reproduce this problem, but happens very often. 
Perhaps the stack trace is enough for someone to figure this out. It 
shows with both Mono 1.9-4 on Windows and 1.9-5 on Fedora 8 64. Didn't 
happen with 1.2, and doesn't happen with MS .NET 2.0.

This stack trace belongs to Mono 1.9-4 on Windows:
  at (wrapper managed-to-native) System.Data.Odbc.libodbc.SQLFreeStmt 
(intptr,System.Data.Odbc.libodbc/SQLFreeStmtOptions) <0x00004>
  at (wrapper managed-to-native) System.Data.Odbc.libodbc.SQLFreeStmt 
(intptr,System.Data.Odbc.libodbc/SQLFreeStmtOptions) <0xffffffff>
  at System.Data.Odbc.OdbcCommand.FreeStatement () [0x00011] in 
C:\cygwin\tmp\monobuild\build\BUILD\mono-1.9\mcs\class\System.Data\System.Data.Odbc\OdbcCommand.cs:370
  at System.Data.Odbc.OdbcCommand.Dispose (bool) [0x0000c] in 
C:\cygwin\tmp\monobuild\build\BUILD\mono-1.9\mcs\class\System.Data\System.Data.Odbc\OdbcCommand.cs:344
  at System.ComponentModel.Component.Finalize () [0x00000] in 
C:\cygwin\tmp\monobuild\build\BUILD\mono-1.9\mcs\class\System\System.ComponentModel\Component.cs:104
  at (wrapper runtime-invoke) 
System.ComponentModel.MarshalByValueComponent.runtime_invoke_void 
(object,intptr,intptr,intptr) <0xffffffff>

This application has requested the Runtime to terminate it in an unusual 
way.
Please contact the application's support team for more information.
Error in my_thread_global_end(): 1 threads didn't exit