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

LP:784848 - The test case for bug #27530 crashes the server in maria-5.3-mwl106

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • None
    • None
    • None

    Description

      The following crash can be observed in the maria-5.3-mwl106 tree:

      igor@sophia:~/maria/maria-5.3-mwl148-mwl106-bugs/mysql-test> ./mysql-test-run --ps-protocol func_str
      Logging: ./mysql-test-run --ps-protocol func_str
      vardir: /home/igor/maria/maria-5.3-mwl148-mwl106-bugs/mysql-test/var
      Checking leftover processes...
      Removing old var directory...
      Creating var directory '/home/igor/maria/maria-5.3-mwl148-mwl106-bugs/mysql-test/var'...
      Installing system database...
      Checking supported features...
      MariaDB Version 5.3.0

      • skipping ndbcluster
      • SSL connections supported
      • binaries are debug compiled
        Collecting tests...
        Using server port 51607

      ==============================================================================

      TEST RESULT TIME (ms)
      ------------------------------------------------------------

      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      main.func_str [ fail ]
      Test ended at 2011-05-18 13:35:55

      CURRENT_TEST: main.func_str
      mysqltest: At line 1203: query 'SELECT * FROM (SELECT * FROM v1) x' failed: 2013: Lost connection to MySQL server during query

      The result from queries just before the failure was:
      < snip >
      1790921346
      4194326291
      2366072709
      2707236321
      CREATE TABLE t2 SELECT CRC32(a) FROM t1;
      desc t2;
      Field Type Null Key Default Extra
      CRC32(a) int(10) unsigned YES NULL
      SELECT * FROM v1;
      C
      2212294583
      450215437
      1842515611
      4088798008
      2226203566
      498629140
      1790921346
      4194326291
      2366072709
      2707236321

      More results from queries before failure can be found in /home/igor/maria/maria-5.3-mwl148-mwl106-bugs/mysql-test/var/log/func_str.log

      Server [mysqld.1 - pid: 29468, winpid: 29468, exit: 256] failed during test run
      Server log from this test:
      ---------SERVER LOG START----------
      110518 13:35:53 [Note] Plugin 'PBXT' is disabled.
      110518 13:35:53 [Note] Plugin 'InnoDB' is disabled.
      110518 13:35:53 [Note] Event Scheduler: Loaded 0 events
      110518 13:35:53 [Note] /home/igor/maria/maria-5.3-mwl148-mwl106-bugs/sql/mysqld: ready for connections.
      Version: '5.3.0-MariaDB-alpha-debug-log' socket: '/home/igor/maria/maria-5.3-mwl148-mwl106-bugs/mysql-test/var/tmp/mysqld.1.sock' port: 16000 Source distribution
      110518 13:35:55 [ERROR] mysqld got signal 11 ;
      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.
      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.

      key_buffer_size=0
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      threads_connected=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 60768 K
      bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Attachments

        Activity

          People

            igor Igor Babaev (Inactive)
            igor Igor Babaev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 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.