In order to troubleshoot issues where wfica process is not behaving properly compared to as expected, we may need to coredump the process so that we can view the function calls in gdb. This articles describes how to generate wfica application core dump

---

Instructions

1.Login into the terminal on the client where Linux Unix Receiver is installed
2.Ensure core dumps are enabled. Make sure ‘ulimit -c unlimited’ is not only included in your current terminal. Better do following as root user.
           $ vi /etc/profile
              Add following lines in the end of the file, then reboot.
             #ulimit –c unlimited
3.Make sure core_pattern file is correctly configured as root:
$> mkdir -p /tmp/cores
$> chmod a+rwx /tmp/cores
$> echo "/tmp/cores/core.%e.%p.%h.%t" > /proc/sys/kernel/core_pattern

*NOTE: The changes done before are onlyapplicable until the next reboot. In order to make the change in all future reboots, you will need to add the following in “/etc/sysctl.conf“:
            kernel.core_pattern=/tmp/cores/core.%e.%p.%h.%t
sysctl.conf is the file controlling every configuration under /proc/sys
1.Reproduce the issue with wfica hang.
2.During wifica hang, use ‘ps’ to find the wfica process id pid. Command is
                           #ps –aux | grep wfica
3.Use kill –s SIGSEGV  <pid from step 5>

You will find the wfica process is killed and a core file like
Core.bash.<pid>.<username>-<hostname>.<time> is generated at /tmp/cores/
1.    To confirm the file format use command
           # cd /tmp/cores/
           # readelf –h Core.bash.<pid>.<username>-<hostname>.<time>,
You can see the file type.

 

            

Type: 

CORE(Core file)

This article explain about the procedure to crash a wfica process for generating core dump