[asterisk-dev] segfault if res_timing_pthread.so loaded
Tilghman Lesher
tlesher at digium.com
Sat Jun 12 21:14:10 CDT 2010
On Saturday 12 June 2010 13:23:21 Katerin wrote:
> Hello, everyone
> I am using asterisk ver 1.6.2.7 with res_timing_pthread.so loaded. I need
> this for conference feature (with confbridge). If I start asterisk
> everything is alright (no errors, warnings in logs), it can also be running
> for one or two weeks and then suddenly crashes with segfault and the
> following message in log file:
>
> Jun 11 21:08:23 asterisk kernel: [77781101.505303] asterisk[15055]:
> segfault at ac ip b79b3e30 sp b46a1cec error 4 in
> res_timing_pthread.so[b79b3000+3000]
>
> I don'd know why this happens. Without res_timing_pthread.so asterisk
> does not crash. I did not have too many calls on it (100-200) at the
> time of crush. There were also no unusual requests coming and what's
> more the confbridge exten was not used...So. If anybody knows how I
> can use this module without asterisk being crashed please share your
> experience.
There are other timing modules in 1.6.2 that are preferred over the pthread
timers, and as you have experienced, it seems that the pthread timers aren't
always reliable. If using Linux, using the DAHDI timers is perhaps the best
available, followed closely by timerfd (which requires a more advanced kernel
than many distributions are yet providing). Also coming up in trunk are
res_timing_kqueue (for *BSD) and res_timing_mach (for Mach-based kernels).
--
Tilghman Lesher
Digium, Inc. | Senior Software Developer
twitter: Corydon76 | IRC: Corydon76-dig (Freenode)
Check us out at: www.digium.com & www.asterisk.org
More information about the asterisk-dev
mailing list