Bug #46355 Crash in clean_up() on mysqld --binlog
Submitted: 23 Jul 2009 12:44 Modified: 14 Apr 2010 11:22
Reporter: Philip Stoev Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.4 OS:Any
Assigned to: Jon Olav Hauglid CPU Architecture:Any

[23 Jul 2009 12:44] Philip Stoev
PeterG found that the following command-line:

./mysqld --binlog 

will crash mysqld. 5.1 is not affected.

How to repeat:
./mysqld --binlog
[23 Jul 2009 12:55] Philip Stoev

#0  0x000000000060315d in clean_up (print_message=true) at mysqld.cc:1460
#1  0x00000000006054f0 in unireg_abort (exit_code=1) at mysqld.cc:1333
#2  0x0000000000608c8a in check_user () at mysqld.cc:1656
#3  main (argc=2, argv=0x7fffffffe5e8) at mysqld.cc:4609

crashing line:

0x000000000060315d in clean_up (print_message=true) at mysqld.cc:1460
1460        sql_print_information(ER_DEFAULT(ER_SHUTDOWN_COMPLETE),my_progname);
[14 Apr 2010 11:22] Jon Olav Hauglid
Closing the bug as "Can't repeat" as the bug is not repeatable
using the current version of mysql-trunk-bugfixing (Ver 5.5.5-m3).