Errores #42

Toma segmentfault

Added by Iñaki Baz Castillo over 2 years ago. Updated over 2 years ago.

Status:Resuelta Start:03/23/2009
Priority:Alta Due date:
Assigned to:Saúl Ibarra Corretgé % Done:

0%

Category:YASS - core
Target version:0.5.0

Description

Estaba yo llamando a * (una prueba de eco con SEMS). Tras establecerse la llamada no se oía nada (puede tener que ver el churro de errores sobre Alsa que salían al arrancar, como ya está reportado por ahí...). Total que llamo, me llega el 200, ACK y tal, no oigo nada, le doy a colgar y:

./yass
 20:50:50.562 os_core_unix.c  pjlib 1.0.1 for POSIX initialized
 20:50:52.263 sip_endpoint.c  Creating endpoint instance...
 20:50:52.264          pjlib  select() I/O Queue created (0x83909b8)
 20:50:52.264 sip_endpoint.c  Module "mod-msg-print" registered
 20:50:52.264 sip_transport.  Transport manager created.
Fallo de segmentación

y el log dice:

 20:51:37.477   tsx0x84de204  State changed from Trying to Completed, event=TX_MSG
 20:51:37.477   dlg0x8461064  Transaction tsx0x84de204 state changed to Completed
 20:51:37.492  strm0x84e227c  Jitter buffer empty (prefetch=0)
 20:51:37.492  strm0x84e227c  Start talksprut..
 20:51:37.532 sip_endpoint.c  Processing incoming message: Request msg ACK/cseq=10 (rdata0x83c9bcc)
 20:51:37.532   pjsua_core.c  RX 404 bytes Request msg ACK/cseq=10 (rdata0x83c9bcc) from UDP 91.121.79.216:5060:
ACK sip:yass@87.218.217.240:5090 SIP/2.0
Via: SIP/2.0/UDP 91.121.79.216;branch=z9hG4bK0c59.67377394.2
Via: SIP/2.0/UDP 91.121.79.216;rport=5080;received=91.121.79.216;branch=z9hG4bKd0QsQaRq
From: <sip:*501@oversip.net>;tag=1ED31A46-49C7E82D00097E7C-40807960
To: <sip:yass@oversip.net>;tag=-MzTkYh07VF8Pn3L7NDyMAAFG0j6sOpZ
Call-ID: WNJ39oFHhrfvW7D1oZjFMJ28q5qj1Qow
Max-Forwards: 10
CSeq: 10 ACK

--end msg--
 20:51:37.532   dlg0x8461064  Received Request msg ACK/cseq=10 (rdata0x83c9bcc)
 20:51:37.532   tsx0x84de204  Request to terminate transaction
 20:51:37.532   tsx0x84de204  State changed from Completed to Terminated, event=USER
 20:51:37.532   dlg0x8461064  Transaction tsx0x84de204 state changed to Terminated
 20:51:37.580   tsx0x84de204  Timeout timer event
 20:51:37.580   tsx0x84de204  State changed from Terminated to Destroyed, event=TIMER
 20:51:37.580  tdta0x84ea2c0  Destroying txdata Response msg 200/INVITE/cseq=10 (tdta0x84ea2c0)
 20:51:37.580   tsx0x84de204  Transaction destroyed!
 20:51:39.373   tsx0x84d9bb4  Timeout timer event
 20:51:39.373   tsx0x84d9bb4  State changed from Completed to Terminated, event=TIMER
 20:51:39.373   dlg0x8461064  Transaction tsx0x84d9bb4 state changed to Terminated
 20:51:39.373   tsx0x84d9bb4  Timeout timer event
 20:51:39.373   tsx0x84d9bb4  State changed from Terminated to Destroyed, event=TIMER
 20:51:39.373  tdta0x84df140  Destroying txdata Request msg ACK/cseq=15265 (tdta0x84df140)
 20:51:39.373   tsx0x84d9bb4  Transaction destroyed!
 20:51:43.797    pjsua_acc.c  Sending 2 bytes keep-alive packet for acc 0 to 91.121.79.216:5060
 20:51:43.797  tdta0x84df140  Destroying txd

History

Updated by Iñaki Baz Castillo over 2 years ago

  • Target version set to 0.5.0

Updated by Saúl Ibarra Corretgé over 2 years ago

Importat changes have been made to the core. Please update to the latest SVN trunk and test again :)

Updated by Iñaki Baz Castillo over 2 years ago

Saúl Ibarra wrote:

Importat changes have been made to the core. Please update to the latest SVN trunk and test again :)

ok, un segundo que estoy instalando Kubuntu Intrepid (KDE4) 64 bits en mi portátil... (no se lo digas al manwe)

Updated by Saúl Ibarra Corretgé over 2 years ago

  • Status changed from Nueva to Resuelta

Lots of changes happened to the core. Access to some important stuf is now protected by locks. Should be fixed now.

It's not reproducible though... :-/

Also available in: Atom PDF