[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
Thu May 20 17:26:14 CDT 2010
The following issue is now in status NEW (again)
======================================================================
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: new
Asterisk Version: SVN
JIRA:
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-05-20 17:26 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-05-20 17:26 tilghman Asterisk Version Older 1.6.1 => SVN
2010-05-20 17:26 tilghman Assigned To tilghman =>
2010-05-20 17:26 tilghman Status assigned => new
======================================================================
More information about the asterisk-bugs
mailing list