| Bug #83738 | Assertion `! is_set()' failed. | ||
|---|---|---|---|
| Submitted: | 8 Nov 2016 9:23 | Modified: | 23 Jan 2019 11:51 | 
| Reporter: | Roel Van de Paar | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | MySQL Server: Security: Privileges | Severity: | S2 (Serious) | 
| Version: | 5.5, 5.5.53 | OS: | Any | 
| Assigned to: | CPU Architecture: | Any | |
   [8 Nov 2016 9:23]
   Roel Van de Paar        
  
 
   [8 Nov 2016 9:38]
   MySQL Verification Team        
  Hello Roel, Thank you for the report. Observed that only debug build(checked 5.5.53) affected. Thanks, Umesh
   [8 Nov 2016 9:39]
   MySQL Verification Team        
  -- 5.5.53 debug build
(gdb) bt
#0  0x00007ff999feb771 in pthread_kill () from /lib64/libpthread.so.0
#1  0x00000000007eecb6 in my_write_core (sig=6) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/mysys/stacktrace.c:433
#2  0x00000000006a695c in handle_fatal_signal (sig=6) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/signal_handler.cc:247
#3  <signal handler called>
#4  0x00007ff99910e5d7 in raise () from /lib64/libc.so.6
#5  0x00007ff99910fcc8 in abort () from /lib64/libc.so.6
#6  0x00007ff999107546 in __assert_fail_base () from /lib64/libc.so.6
#7  0x00007ff9991075f2 in __assert_fail () from /lib64/libc.so.6
#8  0x00000000005722c1 in Diagnostics_area::set_ok_status (this=0x208e308, thd=0x208b710, affected_rows_arg=0, last_insert_id_arg=0, message_arg=0x0)
    at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_error.cc:358
#9  0x000000000059816e in my_ok (thd=0x0, affected_rows=<optimized out>, id=<optimized out>, message=<optimized out>)
    at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_class.h:2959
#10 0x0000000000591d95 in mysql_execute_command (thd=0x208b710) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_parse.cc:3604
#11 0x00000000005943ed in mysql_parse (thd=0x208b710, rawbuf=0x7ff974004bd0 "grant execute on procedure bug0.0 to bug0@localhost", length=<optimized out>, parser_state=0x7ff9826d2c20)
    at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_parse.cc:5780
#12 0x00000000005959ee in dispatch_command (command=COM_QUERY, thd=0x208b710, packet=0x2107381 "grant execute on procedure bug0.0 to bug0@localhost", packet_length=51)
    at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_parse.cc:1038
#13 0x0000000000597124 in do_command (thd=0x208b710) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_parse.cc:773
#14 0x000000000063db66 in do_handle_one_connection (thd_arg=<optimized out>) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_connect.cc:862
#15 0x000000000063dc2f in handle_one_connection (arg=<optimized out>) at /pb2/build/sb_0-20575670-1475079000.51/mysqlcom-pro-5.5.53/sql/sql_connect.cc:781
#16 0x00007ff999fe6df5 in start_thread () from /lib64/libpthread.so.0
#17 0x00007ff9991cf60d in clone () from /lib64/libc.so.6
-- with release build
mysql> grant execute on procedure bug0.0 to bug0@localhost;
ERROR 1548 (HY000): Cannot load from mysql.proc. The table is probably corrupted
mysql> grant execute on procedure bug0.0 to bug0@localhost;
ERROR 1548 (HY000): Cannot load from mysql.proc. The table is probably corrupted
mysql> \q
Bye
 
   [8 Nov 2016 9:42]
   MySQL Verification Team        
  -- 5.6.34 release/debug not affected mysql> grant execute on procedure bug0.0 to bug0@localhost; ERROR 1728 (HY000): Cannot load from mysql.proc. The table is probably corrupted mysql> grant execute on procedure bug0.0 to bug0@localhost; ERROR 1728 (HY000): Cannot load from mysql.proc. The table is probably corrupted mysql> grant execute on procedure bug0.0 to bug0@localhost; ERROR 1728 (HY000): Cannot load from mysql.proc. The table is probably corrupted mysql> grant execute on procedure bug0.0 to bug0@localhost; ERROR 1728 (HY000): Cannot load from mysql.proc. The table is probably corrupted mysql> \q
   [23 Jan 2019 11:51]
   Erlend Dahl        
  5.5 is covered under Oracle Lifetime Sustaining Support and will no longer be supported with updates. See https://www.mysql.com/support/eol-notice.html The bug is not present on 5.6+.
