070304 07:35:08  mysqld started
InnoDB: The first specified data file ./ibdata1 did not exist:
InnoDB: a new database to be created!
070304  7:35:08  InnoDB: Setting file ./ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
070304  7:35:08  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...
070304  7:35:08  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
070304  7:35:09  InnoDB: Started; log sequence number 0 0
070304  7:35:09 [Note] /home/sbester/server/5.0/mysql-5.0.38-linux-i686/bin/mysqld: ready for connections.
Version: '5.0.38-debug'  socket: '/tmp/mysql.sock'  port: 3306  yes
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=8388572
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 = 225788 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8c0bf98
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=0xbe7fe8d8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80def1b handle_segfault + 417
0x83d70dd __pthread_sighandler + 173
0x814bada _Z15setup_sum_funcsP3THDPP8Item_sum + 90
0x8133353 _ZN4JOIN4execEv + 5325
0x8133e7b _Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel + 637
0x82060bb _Z21mysql_derived_fillingP3THDP6st_lexP13st_table_list + 297
0x8205bc2 _Z20mysql_handle_derivedP6st_lexPFbP3THDS0_P13st_table_listE + 82
0x81227ab _Z20open_and_lock_tablesP3THDP13st_table_list + 257
0x80f64a8 _Z21mysql_execute_commandP3THD + 1308
0x80fe98e _Z11mysql_parseP3THDPcj + 380
0x80f4882 _Z16dispatch_command19enum_server_commandP3THDPcj + 1940
0x80f40e2 _Z10do_commandP3THD + 538
0x80f3277 handle_one_connection + 991
0x83d1fb1 pthread_start_thread + 225
0x842ce3a __clone + 106
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 0x8c20e10 = select 1 from ( select sum(`a`) from `t1` group by `a` with rollup) as `a`
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.

Number of processes running now: 0
070304 07:35:27  mysqld restarted
070304  7:35:27  InnoDB: Database was not shut down normally!