Dec  6 15:10:57 sms1 mysqld[19631]: mysqld got signal 11;
Dec  6 15:10:57 sms1 mysqld[19631]: This could be because you hit a bug. It is also possible that this binary
Dec  6 15:10:57 sms1 mysqld[19631]: or one of the libraries it was linked against is corrupt, improperly built,
Dec  6 15:10:57 sms1 mysqld[19631]: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec  6 15:10:57 sms1 mysqld[19631]: We will try our best to scrape up some info that will hopefully help diagnose
Dec  6 15:10:57 sms1 mysqld[19631]: the problem, but since we have already crashed, something is definitely wrong
Dec  6 15:10:57 sms1 mysqld[19631]: and this may fail.
Dec  6 15:10:57 sms1 mysqld[19631]:
Dec  6 15:10:57 sms1 mysqld[19631]: key_buffer_size=16777216
Dec  6 15:10:57 sms1 mysqld[19631]: read_buffer_size=131072
Dec  6 15:10:57 sms1 mysqld[19631]: max_used_connections=15
Dec  6 15:10:57 sms1 mysqld[19631]: max_connections=100
Dec  6 15:10:57 sms1 mysqld[19631]: threads_connected=10
Dec  6 15:10:57 sms1 mysqld[19631]: It is possible that mysqld could use up to
Dec  6 15:10:57 sms1 mysqld[19631]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 848383 K
Dec  6 15:10:57 sms1 mysqld[19631]: bytes of memory
Dec  6 15:10:57 sms1 mysqld[19631]: Hope that's ok; if not, decrease some variables in the equation.
Dec  6 15:10:57 sms1 mysqld[19631]:
Dec  6 15:10:57 sms1 mysqld[19631]: thd=0x8cc40310
Dec  6 15:10:57 sms1 mysqld[19631]: Attempting backtrace. You can use the following information to find out
Dec  6 15:10:57 sms1 mysqld[19631]: where mysqld died. If you see no messages after this, something went
Dec  6 15:10:57 sms1 mysqld[19631]: terribly wrong...
Dec  6 15:10:57 sms1 mysqld[19631]: Cannot determine thread, fp=0x8c7dac4c, backtrace may not be correct.
Dec  6 15:10:57 sms1 mysqld[19631]: Stack range sanity check OK, backtrace follows:
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81bb504
Dec  6 15:10:57 sms1 mysqld[19631]: 0x813d0f1
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81584dd
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82cec22
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82d3277
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82d2a1f
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82d323f
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82d0211
Dec  6 15:10:57 sms1 mysqld[19631]: 0x82d12ac
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81d5682
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81d8800
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81ce5a7
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81ce0cd
Dec  6 15:10:57 sms1 mysqld[19631]: 0x81cd552
Dec  6 15:10:57 sms1 mysqld[19631]: 0x400490bd
Dec  6 15:10:57 sms1 mysqld[19631]: 0x4024e8fe
Dec  6 15:10:57 sms1 mysqld[19631]: New value of fp=(nil) failed sanity check, terminating stack trace!
Dec  6 15:10:57 sms1 mysqld[19631]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack
trace. Resolved
Dec  6 15:10:57 sms1 mysqld[19631]: stack trace is much more helpful in diagnosing the problem, so please do
Dec  6 15:10:57 sms1 mysqld[19631]: resolve it
Dec  6 15:10:57 sms1 mysqld[19631]: Trying to get some variables.
Dec  6 15:10:57 sms1 mysqld[19631]: Some pointers may be invalid and cause the dump to abort...
Dec  6 15:10:57 sms1 mysqld[19631]: thd->query at 0xa6b8778 = call yocBugTest ('hallo2','2')
Dec  6 15:10:57 sms1 mysqld[19631]: thd->thread_id=74153
Dec  6 15:10:57 sms1 mysqld[19631]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Dec  6 15:10:57 sms1 mysqld[19631]: information that should help you find out what is causing the crash.
Dec  6 15:10:57 sms1 mysqld_safe[11077]: Number of processes running now: 0
Dec  6 15:10:57 sms1 mysqld_safe[11079]: restarted
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57  InnoDB: Database was not shut down normally!
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: Starting crash recovery.
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: Reading tablespace information from the .ibd files...
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: Restoring possible half-written data pages from the doublewrite
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: buffer...
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57  InnoDB: Starting log scan based on checkpoint at
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: log sequence number 3 764509532.
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: Doing recovery: scanned up to log sequence number 3 764509532
Dec  6 15:10:57 sms1 mysqld[11082]: InnoDB: Last MySQL binlog file position 0 3428271, file name /var/log/mysql/mysql-bin.000299
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57  InnoDB: Started; log sequence number 3 764509532
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57 [Note] Recovering after a crash using /var/log/mysql/mysql-bin
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57 [Note] Starting crash recovery...
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57 [Note] Crash recovery finished.
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57 [Warning] Found an entry in the 'db' table with empty database name; Skipped
Dec  6 15:10:57 sms1 mysqld[11082]: 061206 15:10:57 [Note] /usr/sbin/mysqld: ready for connections.
Dec  6 15:10:57 sms1 mysqld[11082]: Version: '5.0.27-Debian_0.dotdeb.1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Dotdeb Sarge backport
Dec  6 15:10:59 sms1 mysqld[11082]: mysqld got signal 11;
Dec  6 15:10:59 sms1 mysqld[11082]: This could be because you hit a bug. It is also possible that this binary
Dec  6 15:10:59 sms1 mysqld[11082]: or one of the libraries it was linked against is corrupt, improperly built,
Dec  6 15:10:59 sms1 mysqld[11082]: or misconfigured. This error can also be caused by malfunctioning hardware.
Dec  6 15:10:59 sms1 mysqld[11082]: We will try our best to scrape up some info that will hopefully help diagnose
Dec  6 15:10:59 sms1 mysqld[11082]: the problem, but since we have already crashed, something is definitely wrong
Dec  6 15:10:59 sms1 mysqld[11082]: and this may fail.
Dec  6 15:10:59 sms1 mysqld[11082]:
Dec  6 15:10:59 sms1 mysqld[11082]: key_buffer_size=16777216
Dec  6 15:10:59 sms1 mysqld[11082]: read_buffer_size=131072
Dec  6 15:10:59 sms1 mysqld[11082]: max_used_connections=4
Dec  6 15:10:59 sms1 mysqld[11082]: max_connections=100
Dec  6 15:10:59 sms1 mysqld[11082]: threads_connected=1
Dec  6 15:10:59 sms1 mysqld[11082]: It is possible that mysqld could use up to
Dec  6 15:10:59 sms1 mysqld[11082]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 848383 K
Dec  6 15:10:59 sms1 mysqld[11082]: bytes of memory
Dec  6 15:10:59 sms1 mysqld[11082]: Hope that's ok; if not, decrease some variables in the equation.
Dec  6 15:10:59 sms1 mysqld[11082]:
Dec  6 15:10:59 sms1 mysqld[11082]: thd=0x9d40218
Dec  6 15:10:59 sms1 mysqld[11082]: Attempting backtrace. You can use the following information to find out
Dec  6 15:10:59 sms1 mysqld[11082]: where mysqld died. If you see no messages after this, something went
Dec  6 15:10:59 sms1 mysqld[11082]: terribly wrong...
Dec  6 15:10:59 sms1 mysqld[11082]: Cannot determine thread, fp=0x8c45ec4c, backtrace may not be correct.
Dec  6 15:10:59 sms1 mysqld[11082]: Stack range sanity check OK, backtrace follows:
Dec  6 15:10:59 sms1 mysqld[11082]: 0x81bb504
Dec  6 15:10:59 sms1 mysqld[11082]: 0x813d0f1
Dec  6 15:10:59 sms1 mysqld[11082]: 0x81584dd
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82cec22
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82d3277
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82d2a1f
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82d323f
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82d0211
Dec  6 15:10:59 sms1 mysqld[11082]: 0x82d12ac
Dec  6 15:10:59 sms1 mysqld[11082]: 0x81d5682
Dec  6 15:10:59 sms1 mysqld[11082]: 0x81d8800
Dec  6 15:10:59 sms1 mysqld[11082]: 0x81ce5a7
Dec  6 15:10:59 sms1 mysqld[11082]: Stack trace seems successful - bottom reached
Dec  6 15:10:59 sms1 mysqld[11082]: Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and follow instructions on how to resolve the stack
trace. Resolved
Dec  6 15:10:59 sms1 mysqld[11082]: stack trace is much more helpful in diagnosing the problem, so please do
Dec  6 15:10:59 sms1 mysqld[11082]: resolve it
Dec  6 15:10:59 sms1 mysqld[11082]: Trying to get some variables.
Dec  6 15:10:59 sms1 mysqld[11082]: Some pointers may be invalid and cause the dump to abort...
Dec  6 15:10:59 sms1 mysqld[11082]: thd->query at 0x9d628d0 = call yocBugTest ('hallo2','2')
Dec  6 15:10:59 sms1 mysqld[11082]: thd->thread_id=2