Bug #6955 | SHOW PROCEDURE STATUS crashes the server | ||
---|---|---|---|
Submitted: | 2 Dec 2004 18:04 | Modified: | 6 Dec 2004 6:46 |
Reporter: | Michael G. Zinner | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.2 | OS: | Windows (WinXP) |
Assigned to: | Sergei Glukhov | CPU Architecture: | Any |
[2 Dec 2004 18:04]
Michael G. Zinner
[2 Dec 2004 19:42]
MySQL Verification Team
Thank you for the bug report, the call stack shows the same place as bug #6950: > mysqld.exe!my_utf8_uni(charset_info_st * cs=0x0082c628, unsigned long * pwc=0x03e6e764, const unsigned char * s=0x00951000, const unsigned char * e=0x009585fb) Line 1768 + 0x3 C mysqld.exe!my_ismbchar_utf8(charset_info_st * cs=0x0082c628, const char * b=0x00951000, const char * e=0x009585fb) Line 2257 + 0x15 C mysqld.exe!my_numchars_mb(charset_info_st * cs=0x0082c628, const char * pos=0x00951000, const char * end=0x009585fb) Line 245 + 0x15 C mysqld.exe!String::numchars() Line 547 + 0x25 C++ mysqld.exe!Item_string::Item_string(const char * str=0x009485fc, unsigned int length=65535, charset_info_st * cs=0x0082c628, Derivation dv=DERIVATION_COERCIBLE) Line 858 + 0xb C++ mysqld.exe!create_schema_table(THD * thd=0x00ebe0e0, st_table_list * table_list=0x00eb9608) Line 2945 + 0x2d C++ mysqld.exe!mysql_schema_table(THD * thd=0x00ebe0e0, st_lex * lex=0x00ebe128, st_table_list * table_list=0x00eb9608) Line 3137 + 0x11 C++ mysqld.exe!open_tables(THD * thd=0x00ebe0e0, st_table_list * start=0x00eb9608, unsigned int * counter=0x03e6e8cc) Line 1664 + 0x17 C++ mysqld.exe!open_and_lock_tables(THD * thd=0x00ebe0e0, st_table_list * tables=0x00eb9608) Line 1878 + 0x11 C++ mysqld.exe!mysql_execute_command(THD * thd=0x00ebe0e0) Line 2164 + 0xd C++ mysqld.exe!mysql_parse(THD * thd=0x00ebe0e0, char * inBuf=0x00eb90a8, unsigned int length=21) Line 4662 + 0x9 C++ mysqld.exe!dispatch_command(enum_server_command command=COM_QUERY, THD * thd=0x00ebe0e0, char * packet=0x00eb5041, unsigned int packet_length=22) Line 1507 + 0x1d C++ mysqld.exe!do_command(THD * thd=0x00ebe0e0) Line 1315 + 0x31 C++ mysqld.exe!handle_one_connection(void * arg=0x00ebe0e0) Line 1047 + 0x9 C++ mysqld.exe!pthread_start(void * param=0x00dcb2f8) Line 63 + 0x7 C mysqld.exe!_threadstart(void * ptd=0x00eb4198) Line 173 + 0xd C kernel32.dll!7c80b50b() kernel32.dll!7c8399f3()
[3 Dec 2004 8:47]
Sergei Glukhov
Suggested fix on dev-bugs(subj: Suggested fix for bug#6955, 6950)
[6 Dec 2004 6:46]
Sergei Glukhov
Fixed in 5.0 source tree
[26 Mar 2006 9:00]
Christopher Garside
Just installed the 5.0.19 Community Edition (GA) and bug is still present and repeatable. Has anyone tried 5.1.7 alpha?
[27 Mar 2006 14:23]
Sergei Glukhov
Could you provide a test case?
[28 Mar 2006 2:03]
Christopher Garside
Sergey, I am not sure I know what you are asking for, but: - WinXP SP2, .Net Framework - Upgraded from 5.0 to 5.0.19 - Open monitor and log in as root " Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.0.19-max Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> show procedure status; ERROR 2013 (HY000): Lost connection to MySQL server during query mysql> " What else should I provide?
[29 Mar 2006 9:06]
Sergei Glukhov
I can't repeat this crash. Did you upgrade system tables? Could you send the result of 'show variables like "char%"'?
[29 Mar 2006 9:35]
Christopher Garside
I have not made any specific changes except the initial install. Query result as requested. +--------------------------+---------------------------------------------------------+ | Variable_name | Value | +--------------------------+---------------------------------------------------------+ | character_set_client | latin1 | | character_set_connection | latin1 | | character_set_database | latin1 | | character_set_filesystem | binary | | character_set_results | latin1 | | character_set_server | latin1 | | character_set_system | utf8 | | character_sets_dir | C:\Program Files\MySQL\MySQL Server 5.0\share\charsets\ | +--------------------------+---------------------------------------------------------+ 8 rows in set (0.00 sec) Chris
[29 Mar 2006 10:52]
Sergei Glukhov
System tables have been changed since 5.0.6 see http://dev.mysql.com/doc/refman/5.0/en/news-5-0-6.html "Incompatible change: MyISAM and InnoDB tables created with DECIMAL columns in MySQL 5.0.3 to 5.0.5 will appear corrupt after an upgrade to MySQL 5.0.6. Dump such tables with mysqldump before upgrading, and then reload them after upgrading." Probably you should upgrade your system tables. See also http://dev.mysql.com/doc/refman/5.0/en/mysql-upgrade.html
[31 Mar 2006 2:04]
Christopher Garside
Sergey, Quite right. All is well now. Thank you and my apologies, I should have done a more thorough upgrade job. Regards Christopher