On Thu, 30 Jul 2020 at 19:49, Thomas Dineen <tdineen@xxxxxxxxxxxxx> wrote:
Gentle People:
I have a question about "The Curious Mystery Of Killed Process At 4:56 AM"?
For some while now I have been developing a optimization application, which
depending on the machine may run for several days.
The development process has played out over a month or more of
testing, finding many bugs
including several Segmentation Fault Crashes, which are usually found
and fixed
with the help of GDB.
Now I have a new one: After running for several days the application
terminates,
and prints "Killed" in the shell window. Now know this did not likely
occur via the
keyboard because of physical security. Can a process kill itself? Is
this simply caused
by a bug which must be chased down? Could this be caused by a shortage
of resources?
Memory? Threads? Is there a limit on the number of threads?
I am running GCC 4.4.7 on CentOS 7.0
There should be more details in dmesg and log files. OOM Killer is a
prime suspect.
--
George N. White III
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
