[Bugs] [Bug 1714415] New: Script to make it easier to find hung frames

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1714415

            Bug ID: 1714415
           Summary: Script to make it easier to find hung frames
           Product: GlusterFS
           Version: mainline
            Status: NEW
         Component: scripts
          Assignee: bugs at gluster.org
          Reporter: pkarampu at redhat.com
                CC: bugs at gluster.org
  Target Milestone: ---
    Classification: Community



Description of problem:
    Given a directory with statedumps captured at different times if
    there are any stacks that appear in multiple statedumps, we need a script
which prints them. It would make it easier to reduce time to debug these kinds
of issues.

I developed a script which does this and this is the sample output:
    glusterdump.25425.dump  repeats=5  stack=0x7f53642cb968  pid=0     
unique=0  lk-owner=
    glusterdump.25427.dump  repeats=5  stack=0x7f85002cb968  pid=0     
unique=0  lk-owner=
    glusterdump.25428.dump  repeats=5  stack=0x7f962c2cb968  pid=0     
unique=0  lk-owner=
    glusterdump.25428.dump  repeats=2  stack=0x7f962c329f18  pid=60830 
unique=0  lk-owner=88f50620967f0000
    glusterdump.25429.dump  repeats=5  stack=0x7f20782cb968  pid=0     
unique=0  lk-owner=
    glusterdump.25472.dump  repeats=5  stack=0x7f27ac2cb968  pid=0     
unique=0  lk-owner=
    glusterdump.25473.dump  repeats=5  stack=0x7f4fbc2cb9d8  pid=0     
unique=0  lk-owner=
NOTE: stacks with lk-owner=""/lk-owner=0000000000000000/unique=0 may not be
hung frames and need further inspection

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.