From owner-freebsd-hackers Sat Feb 7 21:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00613 for hackers-outgoing; Sat, 7 Feb 1998 21:23:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00608 for ; Sat, 7 Feb 1998 21:23:18 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id AAA12270; Sun, 8 Feb 1998 00:22:56 -0500 (EST) (envelope-from toor) Message-Id: <199802080522.AAA12270@dyson.iquest.net> Subject: Re: ddb/kgdb: How do I find out what a process is doing? In-Reply-To: <19980208152706.59008@freebie.lemis.com> from Greg Lehey at "Feb 8, 98 03:27:06 pm" To: grog@lemis.com (Greg Lehey) Date: Sun, 8 Feb 1998 00:22:56 -0500 (EST) Cc: hackers@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey said: > I'm doing some kernel development work, and I'm using remote kgdb to > debug it with. I currently have a process which is sleeping > (eternally) in biord. How do I do a backtrace on it? > If the debugger doesn't support using alternate kernel stacks, I usually put a timeout in the tsleep, and call the debugger from the tsleep error return. Seldom should a biord take longer than a few seconds, so perhaps a timeout value of 5*hz should be safe. This, of course, works well only for reproduceable problems. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe hackers" in the body of the message