040222 23:45:35 mysqld startedmysqld got signal 11;This could be because you hit a bug. It is also possible that this binaryor 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 diagnosethe problem, but since we have already crashed, something is definitely wrongand this may fail.

key_buffer_size=16777216read_buffer_size=131072max_used_connections=0max_connections=100threads_connected=0It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 Kbytes of memoryHope that's ok; if not, decrease some variables in the equation.

thd=(nil)Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...Cannot determine thread, fp=0xbffff2c8, backtrace may not be correct.Stack range sanity check OK, backtrace follows:0x80d079f0x4014901c0x82d79940x82d766f0x80d3c3a0x80d1a720x402177a70x80a61d1New 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. Resolvedstack trace is much more helpful in diagnosing the problem, so please do resolve itThe manual page at http://www.mysql.com/doc/en/Crashing.html containsinformation that should help you find out what is causing the crash.