```
kamailio 4.3.0-pre0 (x86_64/linux) e1d68c
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: e1d68c
```
Hi,
Today everything was business as usual, when this happened:
```
May 13 03:40:32 Kamailio2 kamailio[7104]: CRITICAL: <core> [pass_fd.c:275]: receive_fd(): EOF on 23
May 13 03:40:32 Kamailio2 kamailio[7064]: ALERT: <core> [main.c:728]: handle_sigs(): child process 7066 exited by a signal 11
May 13 03:40:32 Kamailio2 kamailio[7064]: ALERT: <core> [main.c:731]: handle_sigs(): core was generated
May 13 03:40:32 Kamailio2 kamailio[7064]: INFO: <core> [main.c:743]: handle_sigs(): terminating due to SIGCHLD
May 13 03:40:32 Kamailio2 kamailio[7068]: INFO: <core> [main.c:794]: sig_usr(): signal 15 received
```
Needless to say, Kamailio crashed (thankfully after hours). No more related logs, unfortunately.
Was wondering if you can tell anything just by the excerpt above.
Thanks.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/158
Building Kamailio from git master on Fedora 22 x86_64 with gcc 5.1.1:
`Makefile.defs:974: You are using an old and unsupported gcc version (5.1.1), compile at your own risk!`
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/230