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

MariaDB SEGV issue

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.9.0, 10.2, 10.3, 10.4, 10.5, 10.6, 10.7, 10.8
    • N/A
    • N/A
    • None
    • Linux jie-2 5.4.143-1-pve #1 SMP PVE 5.4.143-1 (Tue, 28 Sep 2021 09:10:37 +0200) x86_64 x86_64 x86_64 GNU/Linux

    Description

      PoC:

      START TRANSACTION WITH CONSISTENT SNAPSHOT ;
      CREATE TABLE v3 ( v5 INT ( 16 ) , v4 INT ) ENGINE = MEMORY ;
      SELECT v4 IS NULL FROM v3 WHERE '' = 98 ;
      ALTER TABLE v3 ADD ( v6 INT DEFAULT ( ( 'x' IN ( 'x' , 'x' , 'x' , CURRENT_USER , SPACE ( 'x' ) , lower ( 'x' ) ) ) + 91 ) ) ;
      LOCK TABLE v3 WRITE ;
      ALTER TABLE v3 ADD COLUMN ONE INT DEFAULT ( ( ( 'x' = RIGHT ( 'x' , 16 ) ) ) + v4 | CONVERT ( v4 , CHAR ( 23 ) ) ) ;
      

      report (compiled with ASAN):

      Thread pointer: 0x62b00015e218
      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...
      

      I am confused that there is no details in the report. There is also no core dump.

      Attachments

        Issue Links

          Activity

            People

              serg Sergei Golubchik
              fuboat Jingzhou Fu
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.