From owner-freebsd-threads@FreeBSD.ORG Thu Oct 21 20:32:17 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03F1E16A4CE; Thu, 21 Oct 2004 20:32:17 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 796A043D41; Thu, 21 Oct 2004 20:32:16 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9LKVt0f032028; Thu, 21 Oct 2004 16:31:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9LKVt3c032025; Thu, 21 Oct 2004 16:31:55 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 21 Oct 2004 16:31:55 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Michael Nottebrock In-Reply-To: <200410212227.02663.michaelnottebrock@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: threads@freebsd.org cc: Mikhail Teterin cc: kde@freebsd.org cc: current@freebsd.org cc: kde-freebsd@freebsd.kde.org Subject: Re: [kde-freebsd] unkillable multithreaded processes stuck in `STOP' state X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 20:32:17 -0000 On Thu, 21 Oct 2004, Michael Nottebrock wrote: > On Thursday, 21. October 2004 21:23, Mikhail Teterin wrote: > > Hello! > > > > This happened twice already -- first with KMail and now with Kontact. > > A process crashes as usual (KDE's 3.3.0 release was of unusually low > > quality), and seems to go away, except it does not. It stays in the > > `STOP' (according to top(1)) or in the `T' (as per ps(1)) state and > > can not be killed -- neither with -CONT, nor with -KILL. > > [...] > > > This is all, probably, due to something in KDE's attempts to capture > > crashes and collect backtraces for better bug reports. But whatever bugs > > they may have there, having an unkillable process -- of any kind -- worries > > me greatly. Is this a known issue, or is a PR warranted? > > There have been no similar reports (to my knowledge) and I haven't seen > anything similar on either 4.x or 5.x (I don't run 6-CURRENT). Actually, I recall seeing a similar problem about 14 months ago on 5-CURRENT. I believe that when a program crashed, its SIGSEGV handler would fork and attach gdb to its parent in order to generate a stack trace. I didn't have the opportunity to try and track it down, but I also don't remember seeing it in the last six months. It could be because KDE programs crash less for me as opposed to that the bug leading to the wedge has been fixed. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research