sunny, it still kills the 32-bit linux version built as you describe and loaded dynamically. please first run this:

SET GLOBAL innodb_file_format=“Barracuda”;
SET GLOBAL innodb_file_per_table=ON;
\r


080416 11:30:18 mysqld_safe mysqld from pid file /home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/data/box1.hti.co.za.pid ended
080416 11:30:26 mysqld_safe Starting mysqld daemon with databases from /home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/data
080416 11:30:26 [Note] Plugin 'InnoDB' disabled by command line option
080416 11:30:26 [Note] /home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld: ready for connections.
Version: '5.1.25-rc' socket: '/tmp/mysql.sock' port: 3306 yes
080416 11:32:23 InnoDB: Started; log sequence number 46409
080416 11:35:02 InnoDB: Assertion failure in thread 3067284368 in file btr/btr0btr.c line 3235
InnoDB: Failing assertion: page_get_n_recs(page) > 0 || (level == 0 && page_get_page_no(page) == dict_index_get_page(index))
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to [bugs.mysql.com].
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: [dev.mysql.com]
InnoDB: about forcing recovery.
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(print_stacktrace+0x30)[0x82eabfd]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(handle_segfault+0x267)[0x81d70fb]
[0x5eb420]
/lib/i686/nosegneg/libc.so.6(abort+0x101)[0xcbc811]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/lib/mysql/plugin/ha_innodb.so[0x148936]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/lib/mysql/plugin/ha_innodb.so[0x1ff809]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/lib/mysql/plugin/ha_innodb.so[0x23f10a]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x76)[0x829ec2e]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld[0x82b74ea]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_Z17mysql_check_tableP3THDP10TABLE_LISTP15st_ha_check_opt+0x5d)[0x82b7f7d]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_Z21mysql_execute_commandP3THD+0x19db)[0x81e23d1]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_Z11mysql_parseP3THDPKcjPS2_+0x110)[0x81e7d0e]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xa2c)[0x81e87e6]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(_Z10do_commandP3THD+0xf6)[0x81e95de]
/home/sbester/mysql/5.1/mysql-5.1.25-rc-linux-i686/bin/mysqld(handle_one_connection+0xaf2)[0x81dbc68]
/lib/i686/nosegneg/libpthread.so.0[0xde0402]
/lib/i686/nosegneg/libc.so.6(clone+0x5e)[0xd612ae]
080416 11:35:02 - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=8388600
read_buffer_size=131072
max_used_connections=1
max_threads=151
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 337715 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0xa3590f8
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xa365700 = check table table0 extended
thd->thread_id=2
thd->killed=NOT_KILLED