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

innodb.xa_recovery failed in buildbot, mysqld got exception

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 10.0
    • Fix Version/s: 10.0
    • Component/s: Tests
    • Labels:
      None

      Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/7442/steps/test/logs/stdio

      innodb.xa_recovery 'xtradb'              w4 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2018-02-07 19:08:11
      line
      abort() has been called180207 19:08:06 [ERROR] mysqld got exception 0x80000003 ;
       
      Attempting backtrace. You can use the following information to find out
       
      ^ Found warnings in D:/win32-debug/build/mysql-test/var/4/log/mysqld.1.err
      ok
      

      abort() has been called180207 19:08:06 [ERROR] mysqld got exception 0x80000003 ;
      This could be because you hit a bug. It is also possible that this binary
      or one of the libraries it was linked against is corrupt, improperly built,
      or misconfigured. This error can also be caused by malfunctioning hardware.
       
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs
       
      We will try our best to scrape up some info that will hopefully help
      diagnose the problem, but since we have already crashed, 
      something is definitely wrong and this may fail.
       
      Server version: 10.0.35-MariaDB-debug
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=2
      max_threads=501
      thread_count=0
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 195328 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0
      Attempting backtrace. You can use the following information to find out
      where mysqld died. If you see no messages after this, something went
      terribly wrong...
      abort() has been calledGot exception in exception handler!
      180207 19:08:07 [Note] D:/win32-debug/build/sql//Debug/mysqld.exe (mysqld 10.0.35-MariaDB-debug) starting as process 1056 ...
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Git Integration

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