Menu
▾
▴
libodbcxx-devel
|
From: Simon W. <si...@gi...> - 2012-05-23 05:54:25
|
When using the MySQL ODBC driver in a threaded application, I always get the error message: Error in my_thread_global_end(): 1 threads didn't exit I found something about this on the MySQL mailing list: http://article.gmane.org/gmane.comp.db.mysql.odbc/6058/match=my_thread_global_end It looks like it's a known bug. I just wanted to confirm with other users and what the potential issues are of this error. Cheers, Simon -- simonsmicrophone.com |
|
From: Mark K. <gre...@ma...> - 2012-05-24 12:55:34
|
Do you have a sample? I will look into it some more. On May 23, 2012, at 1:55 AM, Simon Walter wrote: > When using the MySQL ODBC driver in a threaded application, I always get > the error message: > Error in my_thread_global_end(): 1 threads didn't exit > > I found something about this on the MySQL mailing list: > http://article.gmane.org/gmane.comp.db.mysql.odbc/6058/match=my_thread_global_end > > It looks like it's a known bug. I just wanted to confirm with other > users and what the potential issues are of this error. > > Cheers, > > Simon > > -- > simonsmicrophone.com > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > libodbcxx-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/libodbcxx-devel |
|
From: Simon W. <si...@gi...> - 2012-06-04 10:47:42
Attachments:
SIGABRT.txt
SIGSEGV.txt
|
On 05/24/2012 09:55 PM, Mark Kromis wrote: > > Do you have a sample? I will look into it some more. I found out that had to do with the driver threading setting which is documented in __handles.c. I set the threading setting to 0, which is supposed to be supported and the default in the latest versions of unixodbc. However, when doing so, I get a SIGABRT and sometimes a SIGSEGV. I've sent a report to the mysql odbc mailing list. I'll see what they say. In the meantime, as it might be related to libodbc++, I'll include the backtraces with this email. Cheers, Simon -- simonsmicrophone.com |
Thanks for helping keep SourceForge clean.
X