[asterisk-bugs] [Asterisk 0015752]: [patch] Thread debugging version of DEADLOCK_AVOIDANCE: wrong line number if re-lock fails.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15752 
====================================================================== 
Reported By:                davidw
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15752
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                       SWP-1516 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-20 13:33 CDT
Last Modified:              2010-07-26 04:20 CDT
====================================================================== 
Summary:                    [patch] Thread debugging version of
DEADLOCK_AVOIDANCE: wrong line number if re-lock fails.
Description: 
As described in https://issues.asterisk.org/view.php?id=15314, if the mutex
referenced by DEADLOCK_AVOIDANCE goes
away, the "Error obtaining mutex: Invalid argument" error message reports
the line number where the lock was originally obtained, not that of the
failure.

This is because DEADLOCK_AVOIDANCE takes special steps to retain the
original line number.  I believe the intent of this is for accurate tracing
of deadlock origins, but I believe that it should be reporting the actual
line number if the actual re-lock call fails.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0015314 [patch] Seg fault in chan_local - local...
====================================================================== 

---------------------------------------------------------------------- 
 (0125005) davidw (reporter) - 2010-07-26 04:20
 https://issues.asterisk.org/view.php?id=15752#c125005 
---------------------------------------------------------------------- 
At the time I tried to test this, 1.6.1.0 was not EOL.

The benefit in fixing this is for the wider Asterisk community, as it will
help in debugging; I'm not sure that I can justify setting up a 1.6.2 test
rig for an issue that is relatively unlikely to affect us in future (we now
know the line numbers are unreliable and can compensate). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-26 04:20 davidw         Note Added: 0125005                          
======================================================================