From: Davy Durham <pubaddr2@davyandbeth.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: /proc question
Date: Fri, 05 Aug 2005 01:31:32 -0500 [thread overview]
Message-ID: <42F307C4.9010503@davyandbeth.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508050823530.20623@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>>I have a zombie process which has apparently died for some unknown reason.. I
>>know it was terminated by a signal (found that from the 9th field (sheduler
>>flags) in /proc/pid/stat)
>>
>>
>
>Start the process under the observation of strace.
>
>
>
>>However, I'm trying to figure out what signal killed it.
>>
>>
>
>
>Jan Engelhardt
>
>
Wish I could.. but it's already happened (to a lot of processes for the
same reason)
It's an intermittant problem and can't really reproduce it at will.
I've redeployed the binary now so I can hopefully attach to it with gdb
to figure out some things next time it does happen.
prev parent reply other threads:[~2005-08-05 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 6:08 /proc question Davy Durham
2005-08-05 6:24 ` Jan Engelhardt
2005-08-05 6:31 ` Davy Durham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42F307C4.9010503@davyandbeth.com \
--to=pubaddr2@davyandbeth.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox