Bug #29800 mysqld got signal 11 and restart when "select . from information_schema.tables"
Submitted: 14 Jul 2007 11:52 Modified: 14 Aug 2007 20:11
Reporter: shijun zhou Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Information schema Severity:S2 (Serious)
Version:5.1.11-beta-log OS:Linux (Linux version 2.4.18-14smp (Red Hat Linux 8.0 3.2-7)) )
Assigned to: CPU Architecture:Any

[14 Jul 2007 11:52] shijun zhou
Description:
Each time I run the following SQL:
select `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` where `TABLE_SCHEMA` = 'flow' and `TABLE_TYPE` = 'BASE TABLE'
Mysqld restarted. Error log looks like :

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=258048
max_used_connections=2
max_connections=100
threads_connected=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 92783 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x8b72558
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=0x4a0d3618, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81affb2
0x4003547e
0x8263ccb
0x8263d73
0x825c69e
0x825b986
0x8298b22
0x829841e
0x829fa45
0x81f79ab
0x81f8dd7
0x81f5291
0x81c4593
0x81cb2d8
0x81c2a9f
0x81c232d
0x81c1874
0x4002f941
0x420da1ca
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/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 0x8b7c2d0 = select `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` where `TABLE_SCHEMA` = 'flow' and `TABLE_TYPE` = 'BASE TABLE'
thd->thread_id=5

Here is the result of resolve_stack_dump
-bash-2.05b$ resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack
0x81affb2 handle_segfault + 430
0x4003547e _end + 931855414
0x8263ccb innobase_read_and_init_auto_inc__11ha_innobasePx + 735
0x8263d73 get_auto_increment__11ha_innobase + 23
0x825c69e get_auto_increment__12ha_partition + 58
0x825b986 info__12ha_partitionUi + 38
0x8298b22 get_schema_tables_record__FP3THDP13st_table_listP8st_tablebPCcT4 + 658
0x829841e get_all_tables__FP3THDP13st_table_listP4Item + 1954
0x829fa45 get_schema_tables_result__FP4JOIN + 377
0x81f79ab exec__4JOIN + 1279
0x81f8dd7 mysql_select__FP3THDPPP4ItemP13st_table_listUiRt4List1Z4ItemP4ItemUiP8st_orderT7T5T7UlP13select_resultP18st_select_lex_unitP13s + 887
0x81f5291 handle_select__FP3THDP6st_lexP13select_resultUl + 225
0x81c4593 mysql_execute_command__FP3THD + 1535
0x81cb2d8 mysql_parse__FP3THDPcUi + 324
0x81c2a9f dispatch_command__F19enum_server_commandP3THDPcUi + 1891
0x81c232d do_command__FP3THD + 189
0x81c1874 handle_one_connection + 764
0x4002f941 _end + 931832057
0x420da1ca _end + 966084994

My Mysql Version:5.1.11-beta-log
my.cnf file is :
[client]
#password       = your_password
port            = 3306
socket          = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[mysqld]
port            = 3306
socket          = /tmp/mysql.sock
skip-locking
key_buffer = 16M
max_allowed_packet = 1M
table_cache = 64
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
default-character-set=gb2312
character-set-server=gb2312
#innodb_force_recovery =6
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 8
default-character-set=gb2312
character_set_client=gb2312
default-storage-engine=INNODB
log-bin=mysql-bin
server-id       = 1
innodb_data_home_dir = /data/
innodb_data_file_path = ibdata1:100M;ibdata2:10M:autoextend
innodb_log_group_home_dir = /data/
innodb_log_arch_dir = /data/

innodb_buffer_pool_size = 96M
innodb_additional_mem_pool_size = 15M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 60M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 2
innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 128M
sort_buffer_size = 128M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

My OS Version:
#1 SMP Wed Sep 4 12:34:47 EDT 2002

How to repeat:
Every Time I call “select `TABLE_NAME` from `INFORMATION_SCHEMA`.`TABLES` where `TABLE_SCHEMA` = 'flow' and `TABLE_TYPE` = 'BASE TABLE'
”From mysql Client Or View database schemas from SQLyog, Mysqld will get signal 11 and  restart.
[14 Jul 2007 16:18] Andy Bang
This is a server bug, not a Merlin bug.
[14 Jul 2007 20:11] Valeriy Kravchuk
Please, try to repeat with a newer version, 5.1.20, and inform about the results.
[14 Aug 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".