I have a mysql 5.0.84-r1 running in Gentoo Linux. If I set "skip-innodb" option in my.cnf config file and issue the following query against INFORMATION_SCHEMA, mysql crashed: mysql> SELECT COUNT(*) FROM `information_schema`.`INNODB_BUFFER_POOL_CONTENT`; ERROR 2013 (HY000): Lost connection to MySQL server during query When innodb enabled in my.cnf all worked whithout crash. I reproduced this crash in all 5.0.x version after 5.0.76. This is my discussion with MySQL developers: http://bugs.mysql.com/bug.php?id=48203 Reproducible: Always Steps to Reproduce: I reproduced this crash in all 5.0.x version after 5.0.76.
*** Bug 289996 has been marked as a duplicate of this bug. ***
Since you're eager to speak to upstream, please report the issue to upstream Percona, and report back. Downgrading priority to minor as it's a status command that only gets issued manually.
I think this is fixed in newer Percona patches, please test 5.0.90.
(In reply to comment #3) > I think this is fixed in newer Percona patches, please test 5.0.90. > For me this still happens with dev-db/mysq-5.0.90-r2. I also have skip-innodb enabled. ---- 100311 1:09:19 - 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=46 max_connections=100 threads_connected=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 93184 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x9c80fb38 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=0x87dca54, backtrace may not be correct. Bogus stack limit or frame pointer, fp=0x87dca54, stack_bottom=0x9cb00000, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x87daa60 = SELECT COUNT(*) FROM `information_schema`.`INNODB_BUFFER_POOL_CONTENT` thd->thread_id=8785 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.
Did you report it to upstream Percona? I didn't hear anything back for more than 3 months, hence why I closed it as TEST-REQUEST. please find or make the upstream (to Percona) bug report, and link here, optionally with a patch.
