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

MythTV SELECT request causes Mariadb server to get a segmentation violation



    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.4.13
    • 10.5.4, 10.4.14
    • Data types
    • Fedora 32 on x86_64


      This was first discovered when trying to watch TV on my MythTV box. The screen went black for a few moments, and then returned to the menu.

      Digging for the cause, I found my way to the mariadb log, which explained the server had got a segmentation violation. I attach a log where I first restart the Mariadb server, then go over to the MythTV machine (not the same box) and select "watch TV". As you can see, it explains it gets signal 11, and then produce a lot of information I hope can help understand what the issue is.

      In that log, there is a SELECT statement. The crash always happens on the same statement. I have tried to run the same statement using the mysql command line tool. I am not able to trigger the problem that way, even after doing a cut-and-paste of the query, even including all the spaces verbatim.

      I also attach the core file produced. (I've been trying to look a little myself, and can see the cause is a null pointer being used, created as sa in Type_handler_string_result::Item_const_eq. But I would need much more understanding why this call produces a null pointer.)

      The mysqld binary is the standard binary from the Fedora distribution, but for convenience I attach that too.


        1. g.glbal
          5 kB
        2. g.local
          5 kB
        3. gdb_output.log
          18 kB
        4. mariadb.log
          14 kB
        5. mysqld.core.xz
          1.41 MB
        6. mysqld.xz
          5.26 MB

        Issue Links



              bar Alexander Barkov
              goeran Göran Uddeborg
              0 Vote for this issue
              2 Start watching this issue



                Git Integration

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