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

mysqld doesn't create core dump if crashing while backtracing or dumping memory

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Not a Bug
    • 10.4.13
    • N/A
    • Server
    • None

    Description

      When a 2nd crash happens in the crash handling routine, the core dump function doesn't get called. As a result, no core file can be obtained and crash can't be analyzed.

      Let's create a config file or command line option to go straight to core dumping in case of crash.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14229 Stack trace is not resolved for shared objects

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-23101 SIGSEGV in lock_rec_unlock() when Galera is enabled

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

          Activity

            Transition Time In Source Status Execution Times
            Rick Pizzi (Inactive) made transition -
            Closed Stalled
            		2h 50m 1
            Rick Pizzi (Inactive) made transition -
            Stalled Open
            		50m 52s 1
            Rick Pizzi (Inactive) made transition -
            Open Closed
            		7h 31m 2

            People

              Unassigned Unassigned
              rpizzi Rick Pizzi (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.