MySQL Bugs: #29497: Ctrl-C in shell causes error in my_thread_global

Bug #29497	Ctrl-C in shell causes error in my_thread_global_end
Submitted:	2 Jul 2007 19:52	Modified:	31 Dec 2007 14:40
Reporter:	Scott Noyes (Basic Quality Contributor)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	5.1.19, 6.0.0	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Hitting <Ctrl-C> at client prompt (not while waiting for a long-running query, just sitting at mysql> prompt) causes error:

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 9
Server version: 5.1.19-beta-community-nt-debug MySQL Community Server (GPL)

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> <Ctrl-C here>Aborted
mysql> Error in my_thread_global_end(): 1 threads didn't exit

How to repeat:
Connect to MySQL with command line client
Type <Ctrl-C>
Wait about 10 seconds

Suggested fix:
Make sure all threads exit on program end, or document this as expected behavior if that is the case.

Thank you for the bug report.

mysql> select version();
+----------------+
| version()      |
+----------------+
| 5.1.21-beta-nt |
+----------------+
1 row in set (0.07 sec)

mysql> mysql> Aborted
Error in my_thread_global_end(): 1 threads didn't exit

This should be a duplicate of Bug#25621.