080605 18:16:37  InnoDB: Started; log sequence number 0 2234476438
080605 18:16:37 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.54-debug-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo Linux mysql-5.0.54
InnoDB: Error: trying to access page number 1737875456 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
080605 18:18:47InnoDB: Assertion failure in thread 2988239760 in file fil0fil.c line 3959
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://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: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html
InnoDB: about forcing recovery.
080605 18:18:47 - mysqld got signal 11;
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=16777216
read_buffer_size=8388608
max_used_connections=9
max_connections=400
threads_connected=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2375680 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xaee21b40
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...
Cannot determine thread, fp=0xb21caff8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81b0963
0x83e3331
0x83c0e82
0x83c14ca
0x83b69a4
0x83cf45c
0x83d7019
0x8373e54
0x8329971
0x836aa32
0x836493c
0x833fbdd
0x83a123a
0x8357ec4
0x829c8bd
0x829d143
0x828bddf
0x826a437
0x82a4c52
0x81cddb0
0x81ce455
0x81ceca9
0x81d0b95
0x444bd15b
0x44401afe
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x8c9b6c0 = CREATE TABLE g2_AccessSubscriberMap(
 g_itemId int(11) NOT NULL,
 g_accessListId int(11) NOT NULL,
 PRIMARY KEY(g_itemId),
 INDEX g2_AccessSubscriberMap_83732(g_accessListId)
) ENGINE=InnoDB
/*!40100 DEFAULT CHARACTER SET utf8 */
thd->thread_id=85
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.