First of all update to the latest version of v1.2.stable or master - it may be something that's already fixed if you're on an old version.
Second, configure FreeSWITCH to save a coredump on a segfault (start it from the init.d script with the -core param).
Once you have a coredump you can open a Jira ticket with a backtrace:
The backtrace will show exactly where and why the segfault occurred, very helpful for debugging.
Any additional info eg FS debug logs would also be helpful.
-Steve
On 18 January 2013 09:23, Mimiko
<vbvbrj@gmail.com> wrote:
New one:
kernel: freeswitch[3559]: segfault at 30 ip 00007fbb945862a4 sp
00007fbb8ef59bc0 error 4 in libfreeswitch.so.1.0.0[7fbb944fb000+277000]
This happened when channels where destroyed after a bridge and a hangup.