Yes, I have access to a C compiler.

You could rebuild having defined #define DEBUG_LOCKS at the top of shared.xs. The problem is then how to relate the addresses displayed: 

 3e56088 waiting - owned by 3ef8c78 shared.xs:1032
 3e56088 waiting - owned by 3ef8c78 shared.xs:1136
 3e56088 waiting - owned by 3ef8c78 shared.xs:1208
 3e56088 waiting - owned by 3ef8c78 shared.xs:1265
 3e56088 waiting - owned by 3ef8c78 shared.xs:347
 3e56088 waiting - owned by 3ef8c78 shared.xs:520
 3e56088 waiting - owned by 3ef8c78 shared.xs:715
 3e56088 waiting - owned by 4001018 shared.xs:1032
 3e56088 waiting - owned by 4001018 shared.xs:1136
 3e56088 waiting - owned by 4001018 shared.xs:1208
 3e56088 waiting - owned by 4001018 shared.xs:1265
 3e56088 waiting - owned by 4001018 shared.xs:347
 3e56088 waiting - owned by 4001018 shared.xs:520
 3e56088 waiting - owned by 4001018 shared.xs:715
 3ef8c78 waiting - owned by 3e56088 shared.xs:1032
 3ef8c78 waiting - owned by 3e56088 shared.xs:1136
 3ef8c78 waiting - owned by 3e56088 shared.xs:1208
 3ef8c78 waiting - owned by 3e56088 shared.xs:1265
 3ef8c78 waiting - owned by 3e56088 shared.xs:347
 3ef8c78 waiting - owned by 3e56088 shared.xs:520
 3ef8c78 waiting - owned by 3e56088 shared.xs:715
 3ef8c78 waiting - owned by 4001018 shared.xs:1032
 3ef8c78 waiting - owned by 4001018 shared.xs:1136
 3ef8c78 waiting - owned by 4001018 shared.xs:1208
 3ef8c78 waiting - owned by 4001018 shared.xs:1265
 3ef8c78 waiting - owned by 4001018 shared.xs:347
 3ef8c78 waiting - owned by 4001018 shared.xs:520
 3ef8c78 waiting - owned by 4001018 shared.xs:715
 4001018 waiting - owned by 3e56088 shared.xs:1032
 4001018 waiting - owned by 3e56088 shared.xs:1136
 4001018 waiting - owned by 3e56088 shared.xs:1208
 4001018 waiting - owned by 3e56088 shared.xs:1265
 4001018 waiting - owned by 3e56088 shared.xs:347
 4001018 waiting - owned by 3e56088 shared.xs:520
 4001018 waiting - owned by 3e56088 shared.xs:715
 4001018 waiting - owned by 3ef8c78 shared.xs:1032
 4001018 waiting - owned by 3ef8c78 shared.xs:1136
 4001018 waiting - owned by 3ef8c78 shared.xs:1208
 4001018 waiting - owned by 3ef8c78 shared.xs:1265
 4001018 waiting - owned by 3ef8c78 shared.xs:347
 4001018 waiting - owned by 3ef8c78 shared.xs:520
 4001018 waiting - owned by 3ef8c78 shared.xs:715

[download]

Back to either thread ids or thread handles: 

tid 3 : handle: 4065f20
tid 2 : handle: 3fd9810
tid 1 : handle: 3f393b0

[download]

The "trick" would be unravelling the defnition of aTHX, but I've never gotten to the bottom of that piece of tortuous magic.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

In reply to Re^5: Debugging lock ownership by BrowserUk
in thread Debugging lock ownership by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.