- make sure error gets propagated to thd->net by calling print_error
- also print the full error message

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

  dont assert if 2 LCP's are being run during a node recovery

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

  fix also undo files

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

  continue on unknown result (no contact)

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

  make free 64 bit (as it represents free bytes, not free extents as originally designed)

  handle undofile/logfile groups that were created while node was node

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

  Not very clever fix for DIH incorrect REDO handling
  - Dont report GCP_SAVE_CONF until first LCP has been complete during NR

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

  In TC init node status for already started nodes during node restart
  (not present in 5.1)

Test that we can start a MySQL Server with a default multibyte charset with
NDB running. Test *really* basic functionality too.

Index: ndb-work/mysql-test/r/rpl_ndb_ctype_ucs2_def.result
===================================================================

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
===================================================================

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

    Add better handling of GCP Stop
    Only kill "offending" node

into  clam.ndb.mysql.com:/space/pekka/ndb/version/my51-bug29176

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.1-new-ndb

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

  Fix 3 problems in REDO validation that could(will) lead to "Error while reading REDO log"

  new support file that I missed during last check ing, sorry

into  mysql.com:/data2/mysql-5.1-new-ndb

  New test cases for generic apply status table
rpl_ndb_dd_advance.test:
  Updated test case to not run sooo long
show_binlog_using_logname.inc, tpcb_disk_data.inc:
  New support file 
rpl_ndb_dd_advance.result:
  Updated result
tpcb.inc:
  New support file for Updated test case to not run sooo long

into  whalegate.ndb.mysql.com:/home/tomas/mysql-5.1-new-ndb