From: Alex Pennace <alex@pennace.org>
To: Christopher Friesen <cfriesen@nortelnetworks.com>
Cc: James Sutherland <jas88@cam.ac.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: unkillable process in R state?
Date: Thu, 11 Oct 2001 18:19:51 -0400 [thread overview]
Message-ID: <20011011181951.A21719@buick.pennace.org> (raw)
In-Reply-To: <Pine.SOL.4.33.0110111918330.24868-100000@orange.csi.cam.ac.uk> <3BC5F0A0.56F644B7@nortelnetworks.com>
In-Reply-To: <3BC5F0A0.56F644B7@nortelnetworks.com>
On Thu, Oct 11, 2001 at 03:18:34PM -0400, Christopher Friesen wrote:
> Okay, I just tried this, and the pertinant results were:
>
> $ gdb find
> GNU gdb 4.18
> Copyright 1998 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "ppc-yellowdog-linux"...(no debugging symbols
> found)...
> (gdb) attach 31075
> Attaching to program: /usr/bin/find, Pid 31075
>
>
>
> At this point it hangs and ctrl-C has no effect and I have to kill it from
> another console.
>
> Attaching to another program worked fine.
>
> Any other ideas?
Look in /proc/31075/fd and see what it has open.
next prev parent reply other threads:[~2001-10-11 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 15:22 NetFilter: Problem in adding additional header using NetFilter Shiva Raman Pandey
2001-10-11 15:53 ` James Sutherland
2001-10-11 16:09 ` Sound on Vaio partially dies between 2.4.5 and 2.4.6 Greg Ingram
2001-10-11 16:48 ` unkillable process in R state? Christopher Friesen
2001-10-11 17:25 ` Ralf Baechle
2001-10-11 18:19 ` Christopher Friesen
2001-10-11 18:19 ` James Sutherland
2001-10-11 19:18 ` Christopher Friesen
2001-10-11 22:19 ` Alex Pennace [this message]
2001-10-11 22:57 ` James Sutherland
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=20011011181951.A21719@buick.pennace.org \
--to=alex@pennace.org \
--cc=cfriesen@nortelnetworks.com \
--cc=jas88@cam.ac.uk \
--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