[jira] [Created] (KUDU-2384) Disable periodic stack trace dumps when running under gdb

["Adar Dembo (JIRA)" <ji...@apache.org>]

Adar Dembo created KUDU-2384:
--------------------------------

             Summary: Disable periodic stack trace dumps when running under gdb
                 Key: KUDU-2384
                 URL: https://issues.apache.org/jira/browse/KUDU-2384
             Project: Kudu
          Issue Type: Bug
          Components: test
    Affects Versions: 1.7.0
            Reporter: Adar Dembo
            Assignee: Todd Lipcon


The new periodic stack trace dump functionality involves sending SIGUSR2 signals between threads from time to time. If you are running a Kudu server or test under gdb, this has the annoying habit of stopping gdb momentarily until you disable it via {{handle SIGUSR2 nostop noprint}}.

Perhaps we should disable this functionality altogether if we're running inside gdb. [This SO post|https://stackoverflow.com/questions/3596781/how-to-detect-if-the-current-process-is-being-run-by-gdb] has some ideas. I also wonder whether we should check for gdb just once at startup or before every dump; the latter would obviate the workaround when attaching to a live server.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)