##### resolve_stack_dump #####
0x8178c7d handle_segfault + 653
0x4017296c _end + 934501788
0x8173574 _Z17mysql_lock_tablesP3THDPP8st_tablej + 468
0x81aec88 _Z11lock_tablesP3THDP13st_table_listj + 184
0x81aea68 _Z20open_and_lock_tablesP3THDP13st_table_list + 168
0x8191311 _Z21mysql_execute_commandP3THD + 12817
0x81d3c6e _Z12execute_stmtP3THDP18Prepared_statement + 462
0x81d38c0 _Z18mysql_stmt_executeP3THDPcj + 384
0x818cfa9 _Z16dispatch_command19enum_server_commandP3THDPcj + 921
0x818cb95 _Z10do_commandP3THD + 133
0x818c0ee handle_one_connection + 782
0x4016cf60 _end + 934478736
0x4030d327 _end + 936183639


####### gdb backtrace output ######
(gdb) bt
#0  0x4025ab71 in kill () from /lib/i686/libc.so.6
#1  0x4016fcf1 in pthread_kill () from /lib/i686/libpthread.so.0
#2  0x0825c63b in ?? ()
#3  0x0002c00b in ?? ()
#4  0x0000000b in ?? ()
#5  0x425b5e38 in ?? ()
#6  0x4035dee0 in _IO_wide_data_2 () from /lib/i686/libc.so.6
#7  0x0000000b in ?? ()
#8  0x4035dee0 in _IO_wide_data_2 () from /lib/i686/libc.so.6
#9  0x425b5e48 in ?? ()
#10 0x08178c40 in ?? ()
#11 0x0000000b in ?? ()
#12 0x084d9276 in ?? ()
#13 0x00000002 in ?? ()
#14 0x08701de8 in ?? ()
#15 0x4017568c in __JCR_LIST__ () from /lib/i686/libpthread.so.0
#16 0x425b5f30 in ?? ()
#17 0x425b5ecc in ?? ()
#18 0x4017296c in __pthread_sighandler () from /lib/i686/libpthread.so.0
Previous frame inner to this frame (corrupt stack?)
(gdb)


####### content of mysql.err ######
040427 22:06:49  InnoDB: Started; log sequence number 0 642356
/GORDON/MySQL/mysql-4.1/dst/libexec/mysqld: ready for connections.
Version: '4.1.2-alpha-max'  socket: '/GORDON/MySQL/data_new/mysql.sock'  port: 9351
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=16384
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 = 19215 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x872a9f8
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=0x425b5e28, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8178c7d
0x4017296c
0x8173574
0x81aec88
0x81aea68
0x8191311
0x81d3c6e
0x81d38c0
0x818cfa9
0x818cb95
0x818c0ee
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 0x8737788 = select col1 FROM test_table where col1=1  union distinct select col1 FROM test_table where col1=2
thd->thread_id=2
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