[asterisk-bugs] [Asterisk 0017037]: [patch] internal_ao2_ref fails to check if null returned from INTERNAL_OBJ
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jul 23 09:34:52 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17037
======================================================================
Reported By: alecdavis
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 17037
Category: Core/General
Reproducibility: random
Severity: crash
Priority: normal
Status: feedback
Target Version: 1.6.2.11
Asterisk Version: SVN
JIRA: SWP-1094
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 252241
Request Review:
======================================================================
Date Submitted: 2010-03-16 05:32 CDT
Last Modified: 2010-07-23 09:34 CDT
======================================================================
Summary: [patch] internal_ao2_ref fails to check if null
returned from INTERNAL_OBJ
Description:
== Spawn extension (phones, 10015, 2) exited non-zero on
'Local/10015 at phones-f860;2'
[Mar 16 23:14:00] ERROR[30417]: astobj2.c:116 INTERNAL_OBJ: bad magic
number 0x0 for 0x85dc240
Bad magic number typically would trigger a segfault.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0017059 What causes 'Bad Magic Number'? As imme...
related to 0016800 astobj2.c:279
has duplicate 0017357 Bad magic number
======================================================================
----------------------------------------------------------------------
(0124907) ramonpeek (reporter) - 2010-07-23 09:34
https://issues.asterisk.org/view.php?id=17037#c124907
----------------------------------------------------------------------
I think I have the same problem reported through issue:
https://issues.asterisk.org/view.php?id=16057
If you read my notes https://issues.asterisk.org/view.php?id=16057#123996
You notice the same problem with local channels and the "/n" option that
seems to fix it.
Since I've upgraded to 1.4.33 the CLI now also displays: "Exceptionally
long voice queue length queuing to Local/xxx@!HG-xxxx", just like mentioned
in this case.
However I have applied the patch mentioned in
https://issues.asterisk.org/view.php?id=17363 which might be the
reason why I don't see the message "Hangup failed! Strange things may
happen!" anymore.
Maybe someone could confirm (or not) my suspected relationship between
these cases?
Issue History
Date Modified Username Field Change
======================================================================
2010-07-23 09:34 ramonpeek Note Added: 0124907
======================================================================
More information about the asterisk-bugs
mailing list