[asterisk-bugs] [Asterisk 0015752]: [patch] Thread debugging version of DEADLOCK_AVOIDANCE: wrong line number if re-lock fails.
Asterisk Bug Tracker
noreply at bugs.digium.com
Sat Jul 24 21:25:16 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
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-24 21:25 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...
======================================================================
----------------------------------------------------------------------
(0124964) pabelanger (manager) - 2010-07-24 21:25
https://issues.asterisk.org/view.php?id=15752#c124964
----------------------------------------------------------------------
Per the Asterisk maintenance timeline page at
http://www.asterisk.org/asterisk-versions maintenance (bug) support for the
1.6.0 and 1.6.1 branches has ended. For continued maintenance support
please move to the 1.6.2 branch.
More information on this change can be found in the release announcement:
http://www.asterisk.org/node/49924
Issue History
Date Modified Username Field Change
======================================================================
2010-07-24 21:25 pabelanger Note Added: 0124964
2010-07-24 21:25 pabelanger Status acknowledged =>
feedback
======================================================================
More information about the asterisk-bugs
mailing list