C ++ application exits with 143 exit code - what does that mean?

My C ++ application crashes periodically. He writes Terminated

in the terminal and stops. I have no idea what the reason is ( gdb

not a solution, this is a multi-threaded application and on a large number of threads the error appears only about what it gdb

cannot handle due to its poor performance). What does exit code 143 mean for CentOS Linux? Does it contain information about the cause of the accident?

+6


source to share


3 answers


143 usually means that the application has caught the signal SIGTERM

, that is, the process has been killed. This could be because another process killed it, or perhaps because the operating system killed it for using too much memory or another resource, etc. This is difficult to understand without additional information.



+20


source


There are several exit codes that have either specific or generally agreed meanings.

In case 143, which is 128 + 15, this means the program died with signal 15, which is SIGTERM



According to the table above, exit codes 1 - 2, 126 - 165, and 255 have special meanings and should therefore be avoided for user-specified exit parameters.

See the table at http://www.tldp.org/LDP/abs/html/exitcodes.html.

+6


source


Error 143 means that the application was killed by some other application or by the OS itself. this error is due to many reasons, such as performing some unauthorized operation, i.e. using user privileges, or the system cannot provide the required drive or directory, or there is a problem in the DNS configuration, or in rare cases an inaccurate floating point result ... but without sufficient information, the reason is difficult to tell ...

0


source







All Articles