[asterisk-bugs] [Asterisk 0017199]: Core dumped

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17199 
====================================================================== 
Reported By:                aleksey2000
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17199
Category:                   Core/General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.6.1.18 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-18 11:16 CDT
Last Modified:              2010-04-19 15:25 CDT
====================================================================== 
Summary:                    Core dumped
Description: 
It happens daily. Depends on channels in use (> 9)
gdb bt:

https://issues.asterisk.org/view.php?id=0  pthread_timer_disable_continuous
(handle=Cannot access memory at
address 0xfec
) at res_timing_pthread.c:240
        timer = (struct pthread_timer *) Cannot access memory at address
0xff8

(gdb) thread apply all bt

Thread 38 (process 2694):
https://issues.asterisk.org/view.php?id=0 0x00000032886c5f3b in read () from
/lib64/libc.so.6
https://issues.asterisk.org/view.php?id=1 0x0000000000555c00 in read_char
(el=0x1ff55ec0, cp=0x7ffff553f9ef "")
at read.c:298
https://issues.asterisk.org/view.php?id=2 0x0000000000550bc0 in el_getc
(el=0x1ff55ec0, cp=0x7ffff553f9ef "") at
read.c:350
https://issues.asterisk.org/view.php?id=3 0x0000000000551020 in el_gets
(el=0x1ff55ec0, nread=0x7ffff5540cbc) at
read.c:243
https://issues.asterisk.org/view.php?id=4 0x000000000043eddd in main (argc=4,
argv=0x7ffff5540ff8) at
asterisk.c:3534
https://issues.asterisk.org/view.php?id=5 0x000000328861d994 in
__libc_start_main () from /lib64/libc.so.6
https://issues.asterisk.org/view.php?id=6 0x0000000000419779 in SSL_accept ()
https://issues.asterisk.org/view.php?id=7 0x00007ffff5540fe8 in ?? ()
https://issues.asterisk.org/view.php?id=8 0x0000000000000000 in ?? ()

Thread 37 (process 2713):
https://issues.asterisk.org/view.php?id=0 0x0000003288e0ad09 in
pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
https://issues.asterisk.org/view.php?id=1 0x00000000005376d6 in __ast_cond_wait
(filename=0x5afc24
"taskprocessor.c", lineno=293,
func=0x5b01f0 "tps_processing_function", cond_name=0x5b0269
"&i->poll_cond", mutex_name=0x5b0252 "&i->taskprocessor_lock",
cond=0x1ff66360, t=0x1ff66398) at
/usr/src/astersik/asterisk-1.6.1.18/include/asterisk/lock.h:827
https://issues.asterisk.org/view.php?id=2 0x0000000000536ffb in
tps_processing_function (data=0x1ff66358) at
taskprocessor.c:293
https://issues.asterisk.org/view.php?id=3 0x000000000054a4e9 in dummy_start
(data=0x1ff57e70) at utils.c:968
https://issues.asterisk.org/view.php?id=4 0x0000003288e06617 in start_thread ()
from /lib64/libpthread.so.0
https://issues.asterisk.org/view.php?id=5 0x00000032886d3c2d in clone () from
/lib64/libc.so.6





In first thread:

Thread 1 (process 11056):
https://issues.asterisk.org/view.php?id=0 pthread_timer_disable_continuous
(handle=Cannot access memory at
address 0xffec
) at res_timing_pthread.c:240
Cannot access memory at address 0x10008
====================================================================== 

---------------------------------------------------------------------- 
 (0120612) tilghman (administrator) - 2010-04-19 15:25
 https://issues.asterisk.org/view.php?id=17199#c120612 
---------------------------------------------------------------------- 
Would it be possible for you to use a different timing source?  We have an
inordinate number of problems with the pthread timers. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-19 15:25 tilghman       Note Added: 0120612                          
======================================================================