CURRENT_TEST: ml_err7
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
040624 15:43:19  InnoDB: Setting file ./ibdata1 size to 50 MB
InnoDB: Database physically writes the file full: wait...
040624 15:43:22  InnoDB: Log file ./ib_logfile0 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile0 size to 5 MB
InnoDB: Database physically writes the file full: wait...
040624 15:43:22  InnoDB: Log file ./ib_logfile1 did not exist: new to be created
InnoDB: Setting log file ./ib_logfile1 size to 5 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Doublewrite buffer not found: creating new
InnoDB: Doublewrite buffer created
InnoDB: Creating foreign key constraint system tables
InnoDB: Foreign key constraint system tables created
040624 15:43:24  InnoDB: Started; log sequence number 0 0
/GORDON/MySQL/mysql-4.1/dst/libexec/mysqld: ready for connections.
Version: '4.1.3-beta-log'  socket: '/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/tmp/master.sock'  port: 9306
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=1048576
read_buffer_size=131072
max_used_connections=1
max_connections=100
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 39423 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8786db8
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=0x42ccdea8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817f35d
0x4017296c
(nil)
0x81db770
0x81db53c
0x8195b6f
0x819bb1d
0x8194d04
0x81941c5
0x81936be
0x4016cf60
0x4030d327
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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 0x879fba8 = explain SELECT (SELECT SUM(1 + 1) FROM t2 ) as scalar_s,
   exists (select 1 from t2) as exists_s,
   (c1 - 4, c1 - 4) in (select c1 + 4 , c1 + 4 from t2) as in_row_s
FROM t_many_col_types, (select c25 x, c32 y from t2) tt WHERE x  = c25
thd->thread_id=1
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
/bin/sh: line 1: 20610 Segmentation fault      /GORDON/MySQL/mysql-4.1/dst/libexec/mysqld --no-defaults --log-bin=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/log/master-bin --server-id=1 --basedir=/GORDON/MySQL/mysql-4.1/dst --port=9306 --local-infile --exit-info=256 --core --datadir=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/master-data --pid-file=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/run/master.pid --socket=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/tmp/master.sock --log=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/log/master.log --character-sets-dir=/GORDON/MySQL/mysql-4.1/dst/share/mysql/charsets --default-character-set=latin1 --tmpdir=/GORDON/MySQL/mysql-4.1/dst/mysql-test/var/tmp --language=/GORDON/MySQL/mysql-4.1/dst/share/mysql/english/ --innodb_data_file_path=ibdata1:50M --open-files-limit=1024 --rpl-recovery-rank=1 --init-rpl-role=master --key_buffer_size=1M --sort_buffer=256K --max_heap_table_size=1M