mysql> select c1 from v2; 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=0x877f9c0 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=0x43441cf8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x819eee7 0x4017b96c 0x402a2de8 0x811b5f5 0x812f83f 0x81e03e9 0x81e63a0 0x8174145 0x8170bab 0x81e53b3 0x81df97d 0x81e6248 0x81eaabe 0x81e60a2 0x81b5367 0x81bbfc6 0x81b3d19 0x81b35f9 0x81b2a65 0x40175f60 0x40307327 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 0x8798bb8 = select c1 from v2 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. ERROR 2013 (HY000): Lost connection to MySQL server during query mysql>mysql> select c1 from v2; 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=0x877f9c0 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=0x43441cf8, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x819eee7 0x4017b96c 0x402a2de8 0x811b5f5 0x812f83f 0x81e03e9 0x81e63a0 0x8174145 0x8170bab 0x81e53b3 0x81df97d 0x81e6248 0x81eaabe 0x81e60a2 0x81b5367 0x81bbfc6 0x81b3d19 0x81b35f9 0x81b2a65 0x40175f60 0x40307327 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 0x8798bb8 = select c1 from v2 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. ERROR 2013 (HY000): Lost connection to MySQL server during query mysql>