Coredumps are generated by the operating system, not FreeSWITCH. See 'man 5 core'.
It is configurable, to an extent. The default is a file named 'core' in the current working directory of the process. You can adjust that behaviour through procfs using /proc/sys/kernel/core_pattern. It can include / characters to set a directory. Note it's a global setting.
For example:
$ echo '/tmp/core.%e.%p' > /proc/sys/kernel/core_pattern
That would result in coredump files being created such as /tmp/core.freeswitch.23523 (example).
You'll want to pick a suitable directory with enough space and suitable permissions.
-Steve
On 29 January 2013 13:22, Mimiko
<vbvbrj@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.
Updated to FreeSWITCH Version 1.3.13b+git~20130118T050605Z~cad607d72e
(git cad607d 2013-01-18 05:06:05Z)
After a many days test it doesn't generate this segfault anymore.
But again in case of coredumps, how to specify where to save this files?
As they does not have permission to fs binary folder.