mysqld.err excerpt

mysqld.crash-excerpt.log (text/plain), 1.42 KB, created by Christian Burger on 2010-10-10 13:18:58 UTC

Version: '5.1.50'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo Linux mysql-5.1.50-r1
101009 12:22:45 - 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=16777216
read_buffer_size=262144
max_used_connections=2
max_threads=151
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133314 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x9304020
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...
stack_bottom = 0xb2e4334c thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x1e) [0x856f36a]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x934c6b0 = select * from Member
thd->thread_id=1
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.