Safety fix to ensure that long event names always ends with \0

This removes a warning about missing DBUG_ENTER while running tests


mysql-test/t/disabled.def:
  Disable test rpl_ndb_multi_update3 that randomly fails on Intel64

mysql-test/t/disabled.def

@@ -33,6 +33,7 @@ rpl_ndb_ddl             : master hangs
 #rpl_ndb_delete_nowhere  : Bug#17400: delete & update of rows in table without pk fails
 rpl_ndb_innodb2ndb      : Bug#18261: Cluster Replication: tests rpl_ndb_xxx2ndb fails
 rpl_ndb_myisam2ndb      : Bug#18261: Cluster Replication: tests rpl_ndb_xxx2ndb fails
+rpl_ndb_multi_update3   : Bug#18627: Cluster Replication: rpl_ndb_multi_update3 fails on Intel 64 bit
 rpl_ndb_log             : result not deterministic, TBD if should remove
 rpl_ndb_relay_space     : Bug#16993
 #rpl_ndb_multi_update3   : Bug#17400: delete & update of rows in table without pk fails

storage/ndb/src/ndbapi/NdbBlob.cpp

@@ -195,8 +195,9 @@ NdbBlob::getBlobEvent(NdbEventImpl& be, const NdbEventImpl* e, const NdbColumnIm
   assert(c->m_blobTable != NULL);
   const NdbTableImpl& bt = *c->m_blobTable;
   // blob event name
-  char bename[MAX_TAB_NAME_SIZE];
+  char bename[MAX_TAB_NAME_SIZE+1];
   getBlobEventName(bename, e, c);
+  bename[sizeof(bename)-1]= 0;
   be.setName(bename);
   be.setTable(bt);
   // simple assigments