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

Fix UBSAN failures

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Done
    • 10.1(EOL), 10.2(EOL), 10.3(EOL), 10.4(EOL)
    • N/A
    • Optimizer

    Description

      According to marko, running tests under UBSAN produces a lot of runtime failures relating to the optimizer (example output attached)

      We need to take these apart and fix them.

      How to reproduce:

      cmake -DWITH_UBSAN=ON

      ...
      run mtr like so

      UBSAN_OPTIONS=print_stacktrace=1:halt_on_error=1 ./mtr alias

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21521 UBSan crashes in MYSQL_BIN_LOG::open

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-21692 UBSAN error: load of value 2779096485, which is not a valid value for type enum_binlog_format

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Task - A task that needs to be done. MDEV-25454 Make MariaDB server UBSAN safe

          • Major - Major loss of function.
          • Confirmed

          Activity

            Transition Time In Source Status Execution Times
            Oleksandr Byelkin made transition -
            Open Confirmed
            		27d 22h 45m 1
            Daniel Black made transition -
            Confirmed Closed
            		1892d 14h 35m 1

            People

              psergei Sergei Petrunia
              psergei Sergei Petrunia
              Votes:
              0 Vote for this issue
              Watchers:
              6 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.