SIGKILL when trying to run under GDB

Aleksey Midenkov midenok at
Wed Jul 2 09:21:35 UTC 2014

It always gets killed at same point:

Loaded symbols for
Reading symbols from
Loaded symbols for

Program terminated with signal SIGKILL, Killed.
The program no longer exists.

I tried to increase ulimits (stack size, open files):

core file size          (blocks, -c) 0
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 20
file size               (blocks, -f) unlimited
pending signals                 (-i) 16382
max locked memory       (kbytes, -l) 64
max memory size         (kbytes, -m) unlimited
open files                      (-n) 4096
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) 32768
cpu time               (seconds, -t) unlimited
max user processes              (-u) unlimited
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

I checked OOM killer. There is enough RAM, overcommit is turned off and no
messages from OOM killer in kernel log. No messages even with
print-fatal-signals = 1.

In light of above facts, I guess that SIGKILL comes from userspace. Who is
sending it then?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the KDevelop-devel mailing list