Reg, by experiment, I can reproduce the 'Killed' error
if I reduce the vmemoryuse limit. Have the default
limits changed between updates?
[root@dev1 ~]# cat hello.c
#include <stdio.h>
int i[100000000];
main()
{
fprintf(stderr,"hello\n");
while (0 == 0) {}
}
[root@dev1 ~]# limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize unlimited
coredumpsize 0 kbytes
memoryuse unlimited
vmemoryuse 10240 kbytes
descriptors 1024
memorylocked 32 kbytes
maxproc 12286
[root@dev1 ~]# ./a.out
Killed
The coredumpsize limit of zero (default I think)
would also prevent coredumps
Cheers,
Terry.
>I have a program here that has been working for several years, and it suddenly
>stopped working. Now it starts running and immediately shows 'Killed'.
>
>The very first line in the program is a fprintf(stderr, ...) and this message
>does not get printed.
>
>And for reasons I dont understand, Linux is not dropping a core file.
>
>Ive recompiled, recompiled with -g, with -ggdb nothing.
>
>How do I get this thing to drop a core file?
>Any possibility that one of the recent (last day or two) fc4 updates could
>cause something like this?
>
>Confused.
>--
> Reg.Clemens
> reg@xxxxxxx
>
>
>--
>fedora-list mailing list
>fedora-list@xxxxxxxxxx
>To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
