[Freeswitch-users] segfault in libfreeswitch.so.1.0.0

[Steven Ayre]

They should go to the cwd, get the FS process and find it by 'ls -ld /proc/PID/cwd'

Also check the ulimit settings, -c limits the size of coredumps.

Steve on iPhone



On 18 Jan 2013, at 19:21, Mimiko <vbvbrj at gmail.com> wrote:

> On 18.01.2013 18:19, Steven Ayre wrote:
>> 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:
>> http://wiki.freeswitch.org/wiki/Reporting_Bugs#Creating_A_Backtrace_With_gdb_.28Linux.2FUnix.29
>> The backtrace will show exactly where and why the segfault occurred,
>> very helpful for debugging.
> 
> Yes, I updated to latest master. Will have to wait as it does not happen 
> regularly or with some pattern. "-core" option I enabled long ago, but 
> as I said, core files are not writted anywhere. A good option or 
> parameter for FS is to specify where to save core dump files.
> 
> -- 
> Mimiko desu.
> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> 
> 
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
> 
> 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