This fixes a problem with SHOW PROCESSLIST

This fixes a possible core dump problem in SHOW PROCESSLIST

into hundin.mysql.fi:/home/heikki/mysql

  Backport from 4.0: fix bug in adaptive hash index search

  Fix a crash in page_dir_find_owner_slot if an adaptive hash index search coincides with purge or an insert

(like FLUSH TABLES).
(Code is already in 4.0)

  Fix bug in PAGE_CUR_LE_OR_EXTENDS search

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

into hegel.local:/home/miguel/dev/mysql-4.0

  Had forgotten to change ha_innodb.cc to reflect that InnoDB now supports HA_READ_PREFIX_LAST

  Backport from 4.1: make sure change_active_index is only called with a properly initialized InnoDB table handle

  Make SHOW INNODB STATUS aware when we are estimating index range size etc.

  Backport from 4.0: fix the BLOB hang if the index tree is of height 1

  Backport from 4.0: fix possible adaprive hash index latch hang

  Fix a typo

  Fix a possible hang at the adaptive hash index latch if MySQL does query estimations also in the middle of a SELECT statement processing

  Make SHOW INNODB STATUS aware which trx's are waiting because of innodb_thread_concurrency exceeded

  Print also the thread ids in SHOW INNODB STATUS also in Linux

Allocate bigger default thread stack because of problems with glibc
Fixed bug in UPDATE ... not_null_field=expression_that_returns_null
Fixed bug in replication when using auto_increment and LOAD DATA INFILE

  Backport the InnoDB HANDLER bug fix from 4.1

  Fix a hang associated with an index tree of height 1 and purging of BLOB fields from it

  Add another diagnostic print to determine why the 'queries inside InnoDB' counter might drift upwards

  Add diagnostic prints to determine why the 'queries inside InnoDB' might drift upwards
ha_innodb.cc:
  Add more print space to SHOW INNODB STATUS; remove possible memory leak in case there is an error

Fixed problem with replication LOAD DATA INFILE when using  --old-rpl-compat.
When executing on master LOAD DATA and InnoDB failed with 'table full' error the binary log was corrupted.