It's a segmentation fault. You get different messages depending on which area of memory it accidentally tried to access.

Run freeswitch with the -core option. If it dies it will coredump, saving all of its memory and state to disk. That lets you find out what it was trying to do when it crashed, and report it on http://jira.freeswitch.org/.

See:
http://wiki.freeswitch.org/wiki/Reporting_Bugs
http://wiki.freeswitch.org/wiki/Debugging_Freeswitch#Simple_bash_script_to_make_debug_easy

-Steve



On 10 February 2011 18:46, Troy Anderson <freeswitch@tlainvestments.com> wrote:
Hi there,

Is there any way to determine what might be the cause of the following message log?  I have this system in a production environment, which makes it difficult to update.  It is running a checkout of FS from Nov 18.  It runs pretty reliably, but once in a while it faults:

kernel: freeswitch[9478] general protection rip:2aaab0f16203 rsp:409f5d08 error:0

Thanks,
Troy
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org