Bug#680412: Error in my_thread_global_end: x threads didn't exit (MySQL bug #57727)

July 05th, 2012 - 02:00 pm ET by Steven Ayre | Report spam

Package: libmyodbc
Version: 5.1.6-1

I am experiencing a lot of these errors in one of my applications:
Error in my_thread_global_end(): 49 threads didn't exit
Error in my_thread_global_end(): 50 threads didn't exit
Error in my_thread_global_end(): 51 threads didn't exit
Error in my_thread_global_end(): 52 threads didn't exit
Error in my_thread_global_end(): 53 threads didn't exit
Error in my_thread_global_end(): 54 threads didn't exit
Error in my_thread_global_end(): 55 threads didn't exit

This appears to be caused by MySQL bug #57727
http://bugs.mysql.com/bug.php?idW727

"The Connector/ODBC driver did not call
mysql_thread_end() when a thread
ended, which caused error messages like: Error in
my_thread_global_end(): 1 threads didn't exit."

It was resolved in rev#999, and is fixed in 5.1.8, however the problem is
still present in the older 5.1.6-1 in Squeeze.

I understand it is unlikely that the Squeeze package can be updated to a
newer version, but is it possible to backport this patch into 5.1.6?


<div>Package: libmyodbc</div><div>Version: 5.1.6-1</div><div><br></div>I am experiencing a lot of these errors in one of my applications:<div><div>Error in my_thread_global_end(): 49 threads didn&#39;t exit</div><div>Error in my_thread_global_end(): 50 threads didn&#39;t exit</div>

<div>Error in my_thread_global_end(): 51 threads didn&#39;t exit</div><div>Error in my_thread_global_end(): 52 threads didn&#39;t exit</div><div>Error in my_thread_global_end(): 53 threads didn&#39;t exit</div><div>Error in my_thread_global_end(): 54 threads didn&#39;t exit</div>

<div>Error in my_thread_global_end(): 55 threads didn&#39;t exit</div></div><div><br></div><div>This appears to be caused by MySQL bug #57727</div><div><a href="http://bugs.mysql.com/bug.php?id=57...t;>http://bugs.mysql.com/bug.php?id=57727</a></div>

<div><span style="background-color:rgb(255,255,255);font-size:12px;line-height:19px;white-space:pre-wrap"><br></span></div><div><span style="background-color:rgb(255,255,255)">&quot;</span><span style="background-color:rgb(255,255,255);font-size:12px;line-height:19px;white-space:pre-wrap">The Connector/ODBC driver did not call</span></div>

<div><span style="background-color:rgb(255,255,255);font-size:12px;line-height:19px;white-space:pre-wrap">mysql_thread_end() when a thread</span></div><div><span style="background-color:rgb(255,255,255);font-size:12px;line-height:19px;white-space:pre-wrap">ended, which caused error messages like: Error in</span></div>

<div><span style="background-color:rgb(255,255,255);font-size:12px;line-height:19px;white-space:pre-wrap">my_thread_global_end(): 1 threads didn&#39;t exit.&quot;</span></div><div><span style="font-size:12px;line-height:19px;white-space:pre-wrap"><br>

</span></div><div><span style="font-size:12px;line-height:19px;white-space:pre-wrap">It was resolved in rev#999, and is fixed in 5.1.8, however the problem is still present in the older 5.1.6-1 in Squeeze.</span></div><div>

<span style="font-size:12px;line-height:19px;white-space:pre-wrap"><br></span></div><div><span style="font-size:12px;line-height:19px;white-space:pre-wrap">I understand it is unlikely that the Squeeze package can be updated to a newer version, but is it possible to backport this patch into 5.1.6?</span></div>





To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
email Follow the discussionReplies 1 replyReplies Make a reply

Replies

#1 Steven Ayre
July 05th, 2012 - 02:40 pm ET | Report spam
The revision fixing this issue is:
http://bazaar.launchpad.net/~myodbc-developers/myodbc/5.1/revision/999



To UNSUBSCRIBE, email to
with a subject of "unsubscribe". Trouble? Contact

Similar topics