Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-3900

Add multi-threaded stack traces

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.2.1
    • Component/s: Core
    • Labels:
      None
    • Sprint:
      MXS-SPRINT-146, MXS-SPRINT-147

      Description

      Recently there have been bugs where the SystemD watchdog kills the MaxScale process due to one of the thread hanging somewhere. This results in a stacktrace that is mostly unhelpful as the signal seems to be delivered to one of the idle threads instead of the thread that actually causes it. To make the stack traces for these cases better, we could use gdb (if installed) to dump all threads.

      It should be as simple as executing the equivalent of:

      gdb --pid=$(pgrep maxscale) -ex 'thr a a bt' -batch
      

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            markus makela markus makela
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.