[Freeswitch-users] segfaults after 24-36 hours
Ivan C Myrvold
ivan at myrvold.org
Mon Aug 6 21:31:19 PDT 2007
I have had it running for almost 3 days now, see details below. IThat
is the longest I have ever running it in the last few months. Do I
need a newer version than 1.0.5567?
UP 0 years, 2 days, 21 hours, 16 minutes, 12 seconds, 521
milliseconds, 415 microseconds
26 sessions since startup
0 sessions
FreeSwitch Version 1.0.5567
Ivan
Den 6. aug. 2007 kl. 22:10 skrev Michael Jerris:
> Can you please svn update to the newest code and see if you can
> reproduce
> the issue now. Also, if you are able to, can you post the details
> you have
> to a bug on jira.freeswitch.org.
>
> Thanks
> Mike
>
>
>
> On 7/29/07 3:51 PM, "Ivan C Myrvold" <ivan at myrvold.org> wrote:
>
>>
>> Den 16. jul. 2007 kl. 07:59 skrev Ivan C Myrvold:
>>
>>>
>>> Den 12. jul. 2007 kl. 23:10 skrev Chris Parker:
>>>
>>>>
>>>> On Jul 12, 2007, at 3:59 PM, Ivan C Myrvold wrote:
>>>>
>>>>>>
>>>>>> Assuming you have the core file:
>>>>>>
>>>>>> gdb -core=<corefile> /path/to/freeswitch
>>>>>>
>>>>>> once you get the gdb prompt issue the command:
>>>>>>
>>>>>> bt
>>>>>
>>>>> Sorry about my stupid questions, but how do I get the core dump?
>>>>>
>>>>> Ivan
>>>>
>>>> It'll probably be much easier to do:
>>>>
>>>> gdb /path/to/freeswitch
>>>>
>>>> gdb> set args <any args you start freeswitch with>
>>>>
>>>> gdb> run
>>>>
>>>> [ FreeSWITCH starts up, then when/if it crashes ]
>>>>
>>>> gdb> bt
>>>>
>>>>
>>>> The output from the end after the 'bt' is what is needed.
>>>>
>>>> -Chris
>>>> -- \\\|||/// \ Chris Parker - Segmentation Fault
>>>> ( core
>>>> dumped )
>>>> \ ~ ~ / \
>>>> | @ @ | \ http://www.segv.org | cparker at segv.org
>>>> oOo (_) oOo \
>>>> -------------------------------------------------------------------
>>>> --
>>>> -
>>>> --
>>>> # OS's are nothing more than device
>>>> drivers! #
>>>>
>>>
>>> Now it crashed again, and here is the bt:
>>> (This is after around 2 days and 16 hours run, on FreeSwitch Version
>>> 1.0.5533 on OS X 10.4.10)
>>>
>>> 2007-07-16 01:27:26 [DEBUG] sofia_reg.c:69 sofia_reg_check_gateway()
>>> registered ip24_37397855
>>> 2007-07-16 01:27:28 [DEBUG] sofia_reg.c:69 sofia_reg_check_gateway()
>>> registered ip24_37397855
>>> nta_agent: tport: Bad message
>>> 2007-07-16 01:27:43 [DEBUG] sofia_reg.c:69 sofia_reg_check_gateway()
>>> registered ip24_37048300
>>> nta_agent: tport: Bad message
>>> 2007-07-16 01:27:47 [DEBUG] sofia_reg.c:69 sofia_reg_check_gateway()
>>> registered ip24_37397855
>>> 2007-07-16 01:27:49 [DEBUG] sofia_reg.c:69 sofia_reg_check_gateway()
>>> registered ip24_37048867
>>>
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: KERN_INVALID_ADDRESS at address: 0xaaaaaaf6
>>> [Switching to process 16385 thread 0x7003]
>>> 0x012bb60f in outgoing_other_destinations (orq=0x326bda0) at nta.c:
>>> 8756
>>> 8756 if (sr->sr_use_a_aaaa || sr->sr_use_srv || sr-
>>> >sr_use_naptr)
>>> (gdb) bt
>>> #0 0x012bb60f in outgoing_other_destinations (orq=0x326bda0) at
>>> nta.c:8756
>>> #1 0x012b7549 in outgoing_tport_error (agent=0x183e000,
>>> orq=0x326bda0, tp=0x325c010, msg=0x326b5b0, error=0) at nta.c:7289
>>> #2 0x0134d981 in tport_pending_error (self=0x325c010, dst=0x0,
>>> error=0) at tport.c:4013
>>> #3 0x01348809 in tport_error_report (self=0x325c010, errcode=0,
>>> addr=0x0) at tport.c:2390
>>> #4 0x013474d3 in tport_close (self=0x325c010) at tport.c:1988
>>> #5 0x01347710 in tport_shutdown (self=0x325c010, how=2) at tport.c:
>>> 2037
>>> #6 0x013499b1 in tport_recv_event (self=0x325c010) at tport.c:2731
>>> #7 0x013495b2 in tport_base_wakeup (self=0x325c010, events=17) at
>>> tport.c:2627
>>> #8 0x01349537 in tport_wakeup (magic=0x6a80f0, w=0x6a91e4,
>>> self=0x325c010) at tport.c:2613
>>> #9 0x01332504 in su_kqueue_port_wait_events (self=0x6a87d0,
>>> tout=1000) at su_kqueue_port.c:558
>>> #10 0x01330778 in su_base_port_run (self=0x6a87d0) at
>>> su_base_port.c:323
>>> #11 0x0133866f in su_port_run (self=0x6a87d0) at su_port.h:314
>>> #12 0x01338646 in su_root_run (self=0x6a9120) at su_root.c:683
>>> #13 0x01337155 in su_pthread_port_clone_main (varg=0xb01f5c58) at
>>> su_pthread_port.c:300
>>> #14 0x90024227 in _pthread_body ()
>>> (gdb)
>>>
>>> Ivan
>>>>
>>>>
>>>> _______________________________________________
>>>> Freeswitch-users mailing list
>>>> Freeswitch-users at lists.freeswitch.org
>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
>>>> users
>>>> http://www.freeswitch.org
>>>>
>>
>> I just tried with the newest FreeSwitch Version 1.0.5547.
>>
>> Here is the log up to the moment it crashed:
>> http://pastebin.freeswitch.org/3141
>>
>> Here is the bt;
>> http://pastebin.freeswitch.org/3143
>>
>> Here is the bt full:
>> http://pastebin.freeswitch.org/3144
>>
>> Hope that someone can fix this, because I am getting tired of
>> restarting FreeSwitch every 1-2 days.
>>
>> Ivan
>>
>>
>>>
>>>
>>> _______________________________________________
>>> Freeswitch-users mailing list
>>> Freeswitch-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
>>> users
>>> http://www.freeswitch.org
>>>
>>
>>
>> _______________________________________________
>> Freeswitch-users mailing list
>> Freeswitch-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
>> users
>> http://www.freeswitch.org
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-
> users
> http://www.freeswitch.org
>
More information about the FreeSWITCH-users
mailing list