From owner-freebsd-current Sun Dec 31 17:56: 3 2000 From owner-freebsd-current@FreeBSD.ORG Sun Dec 31 17:56:02 2000 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2C0E337B400 for ; Sun, 31 Dec 2000 17:56:02 -0800 (PST) Received: from foo.osd.bsdi.com (root@foo.osd.bsdi.com [204.216.28.137]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f011tfh40074; Sun, 31 Dec 2000 17:55:41 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id f011u0s22402; Sun, 31 Dec 2000 17:56:00 -0800 (PST) (envelope-from jhb) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3A4F650D.3212A5C5@eqonline.fi> Date: Sun, 31 Dec 2000 17:56:00 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: User Sja Subject: RE: PROCTREE_LOCK() vs. gdb hang Cc: freebsd-current@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Dec-00 User Sja wrote: > I don't really know my way around the kernel so I'm just guessing here: > > Is there a proctree lock release operation missing in kern_sig.c, > function issignal()? There seems to be one lock operation more > than there are release operations. I tried putting one in and > now gdb doesn't hang the whole machine (at least as easily as > before.) This looks correct. If Paul can test it and commit it that would be most helpful. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message