From owner-freebsd-hackers  Sat Feb  7 21:55:40 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA04657
          for hackers-outgoing; Sat, 7 Feb 1998 21:55:40 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA04619;
          Sat, 7 Feb 1998 21:55:28 -0800 (PST)
          (envelope-from grog@lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id QAA11732;
	Sun, 8 Feb 1998 16:25:10 +1030 (CST)
Received: (from grog@localhost)
          by freebie.lemis.com (8.8.8/8.8.7) id QAA05952;
          Sun, 8 Feb 1998 16:25:09 +1030 (CST)
          (envelope-from grog)
Message-ID: <19980208162509.45093@freebie.lemis.com>
Date: Sun, 8 Feb 1998 16:25:09 +1030
From: Greg Lehey <grog@lemis.com>
To: dyson@FreeBSD.ORG
Cc: hackers@FreeBSD.ORG
Subject: Re: ddb/kgdb: How do I find out what a process is doing?
References: <19980208152706.59008@freebie.lemis.com> <199802080522.AAA12270@dyson.iquest.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.89i
In-Reply-To: <199802080522.AAA12270@dyson.iquest.net>; from John S. Dyson on Sun, Feb 08, 1998 at 12:22:56AM -0500
WWW-Home-Page: http://www.lemis.com/~grog
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sun,  8 February 1998 at  0:22:56 -0500, John S. Dyson wrote:
> 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, 

That's a question.  Does it or doesn't it?  I haven't been able to
find any evidence.

> 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.

Sure, and only for biord.  In this particular case, I know that it's
broken, I was just wondering whether I should take a look at the
nature of the breakage before rebooting the machine.  Recoding the
call to tsleep is overkill.

Greg


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe hackers" in the body of the message