[Asterisk-Users] Tracing a crash with CAPI calls
Armin Schindler
armin at melware.de
Fri Dec 23 02:58:22 MST 2005
On Thu, 22 Dec 2005, Andrew Gough wrote:
...
> OK this here is the backtrace, this crash happened when there was noone
> in the office, I don't know whether there was an inbound call at the
> time or not. I hope this is what you need, Let me know if you need
> anything else. There does not seem to be any pattern to the crashes.
> Today I was on an outbound call over CAPI ISDN for 25 minutes, during
> which several other inbound, outbound calls were made, and suddenly it
> crashed, ending my call. Then the crash BTed below happened when there
> was noone in the office. Any help would be much appreciated, as I will
> have to regretfully give up on Asterisk if I can't get a solution. If
> you need the actual core dump it is at
> http://dev.gcdtech.com/core.tar.gz
>
> Andrew Gough
>
> #0 0x400268b7 in pthread_mutex_trylock () from /lib/tls/libpthread.so.0
> No symbol table info available.
> #1 0x0806c146 in ast_mutex_trylock (pmutex=0x672e33fc) at lock.h:597
> No locals.
> #2 0x0806175a in ast_queue_hangup (chan=0x672e3330) at channel.c:671
> f = {frametype = 4, subclass = 1, datalen = 0, samples = 0,
> mallocd = 0, offset = 0, src = 0x0, data = 0x0, delivery = {tv_sec =
> 0,
> tv_usec = 0}, prev = 0x0, next = 0x0}
> #3 0x408fc2d9 in __sip_autodestruct (data=0x81be208) at chan_sip.c:1315
> p = (struct sip_pvt *) 0x81be208
> #4 0x08056c3e in ast_sched_runq (con=0x8172f28) at sched.c:373
> current = (struct sched *) 0x8174868
> tv = {tv_sec = 1135275568, tv_usec = 989877}
> x = 0
> res = 1083432672
> #5 0x40927e28 in do_monitor (data=0x0) at chan_sip.c:11253
> res = 0
> sip = (struct sip_pvt *) 0x0
> peer = (struct sip_peer *) 0x0
> t = 1135275568
> fastrestart = 0
> lastpeernum = -1
> curpeernum = 6
> reloading = 0
> #6 0x40024b63 in start_thread () from /lib/tls/libpthread.so.0
> No symbol table info available.
> #7 0x401ac18a in clone () from /lib/tls/libc.so.6
> No symbol table info available.
This looks like an asterisk internal problem (or chan_sip)...
Armin
More information about the asterisk-users
mailing list