Re: SIGKILL
On 17 Mar, 20:28, Ian Collins <ian-n...@hotmail.com> wrote:
On 03/18/10 09:20 AM, cerr wrote:
I had to add a certain portion of code to an application
which had been considered to run stable (bewfore my
addition). Now the QA guy came back to me saying that he's
seeing a SIGKILL after a while (several hours) since my code
addition. The code I added simply writes a string
(PIDMessageBuf - declared private) and a at runtime
generated timestamp into a text file a la:
[code]
<snip>
[/code]
I cannot see how this code would lead to a SIGKILL, anyone?
Oh by the way, this is running in a threaded while(1) loop
that comes around once a second. Any hints or suggestions
are greatly appreciated!
Get them to either a) send you a core or b) run the code in a debugger
and give you a shout when it aborts.
SIGKILL doesn't give a core. I don't even know if you can do
anything with it in the debugger. And it almost always comes
from outside the process. I'd guess that there's something
monitoring the processes in the environment, which decides that
his process is up to no good, so kills it. Maybe his
modification makes some monitoring software think it's a virus.
--
James Kanze