[asterisk-bugs] [Asterisk 0014920]: Segmentation fault after almost exactly ~ 500 finished SIP over TCP calls.
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 17 14:10:31 CDT 2009
The following issue has been UPDATED.
======================================================================
http://bugs.digium.com/view.php?id=14920
======================================================================
Reported By: vrban
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14920
Category: Channels/chan_sip/TCP-TLS
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 188895
Request Review:
======================================================================
Date Submitted: 2009-04-16 20:35 CDT
Last Modified: 2009-04-17 14:10 CDT
======================================================================
Summary: Segmentation fault after almost exactly ~ 500
finished SIP over TCP calls.
Description:
I reproducibility get a Segmentation fault after almost exactly ~ 500 SIP
over TCP calls.
To ensure this is TCP related i have done the same test with SIP over UDP
-> no crash.
The gdb output:
astmm.c line 132 (__ast_alloc_region): '®lock' really deep reentrancy!
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb29ffb90 (LWP 13758)]
0x080852be in __ast_pthread_mutex_unlock (filename=0x81b846c "astmm.c",
lineno=135, func=0x81b8759 "__ast_alloc_region", mutex_name=0x81b84d1
"®lock",
t=0x8215560) at
/home/systemvi/src/asterisk-trunk/include/asterisk/lock.h:685
685 if (lt->reentrancy && (lt->thread[lt->reentrancy-1] !=
pthread_self())) {
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-04-17 14:10 tilghman Description Updated
======================================================================
More information about the asterisk-bugs
mailing list