Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

My OOMon crashed or disconnected with the message “Abnormal termination.” What happened?

April 26, 2017crashed disconnected happened message oomon

0

Posted

My OOMon crashed or disconnected with the message “Abnormal termination.” What happened?

1 Answer

0

Posted

Your OOMon appears to have crashed due to a bug. You can help me out by filling out a bug report containing the following information: • The version of OOMon you were running if it was an official release. If it was from CVS, the date and time of the checkout. If it was a from a snapshot tarball, the date of the snapshot. • A description of what you were doing when OOMon crashed. • The last 5 to 10 lines of your oomon.log file: tail -10 oomon.log • A full backtrace of the crash using the GDB debugger: Find the location of the resulting core file. It’s usually called “oomon.core” or just “core”. Change to the directory containing the source code to your OOMon. The version of the source code MUST match the version of the executable that crashed Run GDB: gdb Make sure you replace “” with the OOMon executable filename that crashed and “” with the resulting core filename. At the “(gdb)” prompt, type the following command: bt full Please copy the entire ou