From owner-freebsd-threads@FreeBSD.ORG Fri Oct 22 01:47:23 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 E1D9A16A4CE for ; Fri, 22 Oct 2004 01:47:23 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D93143D1D for ; Fri, 22 Oct 2004 01:47:23 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.93] ([66.127.85.93]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id i9M1lHWi055258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 21 Oct 2004 18:47:17 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <417866BF.1000200@errno.com> Date: Thu, 21 Oct 2004 18:47:43 -0700 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 0.8 (Macintosh/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: kde@freebsd.org cc: current@freebsd.org cc: Mikhail Teterin cc: kde-freebsd@freebsd.kde.org cc: threads@freebsd.org cc: Michael Nottebrock 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: Fri, 22 Oct 2004 01:47:24 -0000 Robert Watson wrote: > 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. On my recent -current laptop (updated last week) I can reliably run gdb on a program, break main, and quit. The process being debugged is left in STOP state and is unkillable. Sam