Reserve the MySQL LOCK_thread_count mutex when printing thd->query of
an arbitrary transaction; if we are printing thd->query of a transaction that
we know is currently executing inside InnoDB, then we know that MySQL cannot
meanwhile change thd->query, and no need to reserve the MySQL mutex; note
that this patch still leaves open the possibility of races in MySQL's
thd->query_len

into mysql.com:/space/my/mysql-4.0

  A flawed fix of the thd->query race in SHOW INNODB STATUS; see the comments in code about how to fix this properly; we cannot use LOCK_thread_count to protect thd->query, because that will cause a deadlock of threads

into mysql.com:/space/my/mysql-4.0-build

   make_binary_distribution (bug#2857)

  innobase_mysql_print_thd(): protect thd with LOCK_thread_count (Bug #3596)

  Backport suppression of MSVC++ warning from 4.1

 - Tagged ChangeSet@1.1800.1.1 as "mysql-4.0.19"

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

into hundin.mysql.fi:/home/marko/j/mysql-4.0

into mysql.com:/home/mydev/mysql-4.0-bug2831

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

"phrase search" should not match partial words (it should not match 'paraphrase searches')

into mysql.com:/home/mydev/mysql-4.0-bug2831

into hundin.mysql.fi:/home/marko/l/mysql-4.0

into mysql.com:/home/mydev/mysql-4.0-bug2831

into a80-186-24-72.elisa-laajakaista.fi:/home/my/bk/mysql-4.0

to use long query strings with it.
Bug#3633

into mysql.com:/home/mysql_src/mysql-4.0

into mysql.com:/home/mysql_src/mysql-4.0

very minor changes: a STOP SLAVE in a replication test to get rid of a non critical message in slave.err,
and a comment update

(Bug #3596)

into hundin.mysql.fi:/home/marko/l/mysql-4.0

just for beauty of truth.