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

Assertion `0' in Protocol::end_statement upon fulltext search in blackhole table

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL)
    • 10.5, 10.6, 10.11
    • Full-text Search
    • None

    Description

      Filing for the record. I don't see any practical importance in this.

      INSTALL SONAME 'ha_blackhole';
      		 
      CREATE TABLE t (
      		 
        f char(255),
      		 
        fulltext key (f)
      		 
      ) ENGINE=BLACKHOLE;
      		 
      SELECT * FROM t WHERE MATCH (f) AGAINST ('wear' WITH QUERY EXPANSION);

      10.4 99ee200b

      		 
      mysqld: /src/sql/protocol.cc:619: void Protocol::end_statement(): Assertion `0' failed.
      		 
      230320 16:42:50 [ERROR] mysqld got signal 6 ;
      		 
       
      		 
      #7  0x00007fb99ee45472 in __GI_abort () at ./stdlib/abort.c:79
      		 
      #8  0x00007fb99ee45395 in __assert_fail_base (fmt=0x7fb99efb9a70 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55e777d3e080 "0", file=0x55e777d3d580 "/home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/protocol.cc", line=619, function=<optimized out>) at ./assert/assert.c:92
      		 
      #9  0x00007fb99ee53df2 in __GI___assert_fail (assertion=0x55e777d3e080 "0", file=0x55e777d3d580 "/home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/protocol.cc", line=619, function=0x55e777d3df60 "void Protocol::end_statement()") at ./assert/assert.c:101
      		 
      #10 0x000055e775d3aec7 in Protocol::end_statement (this=0x62b00005b808) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/protocol.cc:619
      		 
      #11 0x000055e775fef908 in dispatch_command (command=COM_QUERY, thd=0x62b00005b208, packet=0x62900023f209 "SELECT * FROM t WHERE MATCH (f) AGAINST ('wear' WITH QUERY EXPANSION)", packet_length=69, is_com_multi=false, is_next_command=false) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/sql_parse.cc:2441
      		 
      #12 0x000055e775fe8cb4 in do_command (thd=0x62b00005b208) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/sql_parse.cc:1378
      		 
      #13 0x000055e7763d894a in do_handle_one_connection (connect=0x608000000da8) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/sql_connect.cc:1420
      		 
      #14 0x000055e7763d8230 in handle_one_connection (arg=0x608000000da8) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/sql/sql_connect.cc:1324
      		 
      #15 0x000055e777012c7b in pfs_spawn_thread (arg=0x615000004e08) at /home/jenkins/workspace/sandbox-elenst/Nightly-Build-CS/src/storage/perfschema/pfs.cc:1869
      		 
      #16 0x00007fb99eea7fd4 in start_thread (arg=<optimized out>) at ./nptl/pthread_create.c:442
      		 
      #17 0x00007fb99ef2866c in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81

      No obvious problem with a non-debug build.

      Attachments

        Activity

          No workflow transitions have been executed yet.

          People

            Unassigned Unassigned
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.