Bug #44816 | mysqld crashes in Item_func::print on SHOW CREATE TABLE | ||
---|---|---|---|
Submitted: | 12 May 2009 7:54 | Modified: | 25 Jun 2009 12:17 |
Reporter: | Christian Rishoj | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: General | Severity: | S1 (Critical) |
Version: | 5.0.79, 5.1.32 | OS: | Any (Debian Lenny) |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash |
[12 May 2009 7:54]
Christian Rishoj
[12 May 2009 8:01]
Christian Rishoj
Possible reason: The view definition refers to another view (`recentMovers`), which does not exist (it has been deleted).
[12 May 2009 8:33]
Sveta Smirnova
Thank you for the report. Yes, we are not able to reproduce the problem using generic view. Please provide output of SHOW CREATE TABLE for all underlying tables and views.
[12 May 2009 14:24]
Christian Rishoj
I have attached a structural dump. A quick trial of loading the structure, dropping the referred view and inspecting the referring view on my local box did not reproduce the problem, though.
[13 May 2009 10:26]
Sveta Smirnova
Thank you for the feedback. Problem still not repeatable for me. Additionally there is a chance this was fixed after 5.1.32. Could you please try current version 5.1.34 and if problem still exists provide more information related to the problem: dump of tables or output of SHOW TABLE STATUS for all underlying tables and your configuration file.
[13 May 2009 11:45]
Christian Rishoj
The tables have since been dropped and re-created, so I am afraid I can no longer reproduce this error or provide TABLE STATUS output.
[19 May 2009 14:29]
MySQL Verification Team
I couldn't repeat too.
[20 May 2009 6:30]
Sveta Smirnova
Thank you for the feedback. As 2 of us can not repeat the problem and problem is not repeatable on you side I close the report as "Can't repeat". If you meet this again and would be able to provide more details how to repeat feel free to open the report.
[30 Oct 2009 8:23]
MySQL Verification Team
repeatable in 5.0.77, and 5.0.79, but not repeatable in 5.0.82.. mysqld-debug.exe!Item_sum::print()[item_sum.cc:449] mysqld-debug.exe!Item::print_item_w_name()[item.cc:443] mysqld-debug.exe!st_select_lex::print()[sql_select.cc:15847] mysqld-debug.exe!st_select_lex_unit::print()[sql_lex.cc:1625] mysqld-debug.exe!view_store_create_info()[sql_show.cc:1288] mysqld-debug.exe!mysqld_show_create()[sql_show.cc:433] mysqld-debug.exe!mysql_execute_command()[sql_parse.cc:3526] mysqld-debug.exe!mysql_parse()[sql_parse.cc:6313] mysqld-debug.exe!dispatch_command()[sql_parse.cc:1938] mysqld-debug.exe!do_command()[sql_parse.cc:1628] mysqld-debug.exe!handle_one_connection()[sql_parse.cc:1234] mysqld-debug.exe!pthread_start()[my_winthread.c:85] mysqld-debug.exe!_threadstart()[thread.c:196] kernel32.dll!FlsSetValue()
[4 May 2010 5:12]
MySQL Verification Team
the fix for bug #43354 might have fixed this too