BUG#27404 util thd mysql_parse sig11 when mysqld default multibyte charset

NDB util thread calls mysql_parse internally with plain old c strings (7bit ascii) to create tables (e.g. mysql.ndb_schema). With mysqld default charset set to a multibyte one (e.g. ucs2) mysql_parse would try to interpret the 7bit string as UCS2 and promptly explode in a heap.

Solution is to set the util thread to be using utf8 charset.

Index: ndb-work/sql/ha_ndbcluster.cc
===================================================================
--- ndb-work.orig/sql/ha_ndbcluster.cc	2007-05-15 16:05:27.748009750 +0200
+++ ndb-work/sql/ha_ndbcluster.cc	2007-05-15 16:58:48.720058000 +0200
@@ -8909,6 +8909,14 @@ pthread_handler_t ndb_util_thread_func(v
   thd->main_security_ctx.priv_user = 0;
   thd->current_stmt_binlog_row_based= TRUE;     // If in mixed mode
 
+  CHARSET_INFO *charset_connection;
+  charset_connection= get_charset_by_csname("utf8",
+                                            MY_CS_PRIMARY, MYF(MY_WME));
+  thd->variables.character_set_client= charset_connection;
+  thd->variables.character_set_results= charset_connection;
+  thd->variables.collation_connection= charset_connection;
+  thd->update_charset();
+
   /* Signal successful initialization */
   ndb_util_thread_running= 1;
   pthread_cond_signal(&COND_ndb_util_ready);