Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-8280

crash in 'show global status' with --skip-grant-tables!

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.5
    • 10.1.6
    • Admin statements
    • None
    • Win x64
    • 10.1.6-1

    Description

      Version: '10.1.5-MariaDB' mariadb.org binary distribution
      [ERROR] mysqld got exception 0xc0000005 ;
      mysqld.exe!show_column_grants()[sql_acl.cc:10388]
      mysqld.exe!show_status_array()[sql_show.cc:3147]
      mysqld.exe!show_status_array()[sql_show.cc:3155]
      mysqld.exe!fill_status()[sql_show.cc:7112]
      mysqld.exe!get_schema_tables_result()[sql_show.cc:7965]
      mysqld.exe!JOIN::exec_inner()[sql_select.cc:2545]
      mysqld.exe!JOIN::exec()[sql_select.cc:2396]
      mysqld.exe!mysql_select()[sql_select.cc:3326]
      mysqld.exe!handle_select()[sql_select.cc:373]
      mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5797]
      mysqld.exe!execute_show_status()[sql_parse.cc:5830]
      mysqld.exe!mysql_execute_command()[sql_parse.cc:2871]
      mysqld.exe!mysql_parse()[sql_parse.cc:7178]
      mysqld.exe!dispatch_command()[sql_parse.cc:1473]
      mysqld.exe!do_command()[sql_parse.cc:1093]
      mysqld.exe!threadpool_process_request()[threadpool_common.cc:233]
      mysqld.exe!io_completion_callback()[threadpool_win.cc:568]

      How To Repeat:
      ---------------------

      Start server: mysqld.exe --no-defaults --skip-grant-tables --console

      show global status;

      Attachments

        Activity

          People

            cvicentiu Vicențiu Ciorbaru
            sbester1 sbester1
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.