sbester@linux:~/server/5.0/mysql-standard-5.0.26-linux-i686-glibc23> ./bin/resolve_stack_dump -s ./bin/mysqld.sym ./data/crash_on_startup_after_freeing_disk_space.txt 
061028 13:54:16  mysqld started
061028 13:54:16 [Warning] No argument was provided to --log-bin, and --log-bin-index was not used; so replication may break when this MySQL server acts as a master and has his hostname changed!! Please use '--log-bin=linux-bin' to avoid this problem.
061028 13:54:16  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
061028 13:54:16  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 17 1586084578.
InnoDB: Doing recovery: scanned up to log sequence number 17 1586165220
InnoDB: Transaction 0 12713584 was in the XA prepared state.
InnoDB: 1 transaction(s) which must be rolled back or cleaned up
InnoDB: in total 0 row operations to undo
InnoDB: Trx id counter is 0 12713984
061028 13:54:16  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 61207, file name ./linux-bin.000237
061028 13:54:17  InnoDB: Started; log sequence number 17 1586165220
061028 13:54:17  InnoDB: Starting recovery for XA transactions...
061028 13:54:17  InnoDB: Transaction 0 12713584 in prepared state after recovery
061028 13:54:17  InnoDB: Transaction contains changes to 1 rows
061028 13:54:17  InnoDB: 1 transactions in prepared state after recovery
061028 13:54:17 [Note] Found 1 prepared transaction(s) in InnoDB
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=0
read_buffer_size=1044480
max_used_connections=0
max_connections=500
threads_connected=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 765996 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=(nil)
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=0xbfffd9ac, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x817adf8 handle_segfault + 356
0x82f20fb trx_sig_send + 231
0x82ed4c3 trx_rollback_step + 179
0x829be9a que_thr_step + 446
0x829b525 que_run_threads + 45
0x82eafde trx_general_rollback_for_mysql + 158
0x82ed598 trx_rollback_for_mysql + 32
0x8225598 _Z24innobase_rollback_by_xidP5xid_t + 68
0x821c8e5 _Z10ha_recoverP7st_hash + 453
0x817d405 _Z22init_server_componentsv + 537
0x817b305 main + 417
0x400d0e80 _end + 934318224
0x8103981 _start + 33
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
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
061028 13:54:18  mysqld ended
sbester@linux:~/server/5.0/mysql-standard-5.0.26-linux-i686-glibc23>