NetBSD Problem Report #45770

From dholland@netbsd.org  Mon Jan  2 17:26:27 2012
Return-Path: <dholland@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by www.NetBSD.org (Postfix) with ESMTP id 09CD663B954
	for <gnats-bugs@gnats.NetBSD.org>; Mon,  2 Jan 2012 17:26:27 +0000 (UTC)
Message-Id: <20120102172632.9D83414A261@mail.netbsd.org>
Date: Mon,  2 Jan 2012 17:26:32 +0000 (UTC)
From: dholland@netbsd.org
Reply-To: dholland@netbsd.org
To: gnats-bugs@gnats.NetBSD.org
Subject: there should be a ddb command to wake up a lwp
X-Send-Pr-Version: 3.95

>Number:         45770
>Category:       kern
>Synopsis:       there should be a ddb command to wake up a lwp
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 02 17:30:00 +0000 2012
>Originator:     David A. Holland
>Release:        current of 20120101
>Organization:
>Environment:
irrelevant

>Description:

Sometimes when one is working on a broken kernel in ddb it becomes
desirable to reawaken a sleeping process. The obvious case of this is
where there's a deadlock, you've found it, and you want to get the
system unstuck again; it's easy enough to clear the offending mutex,
but reawakening one of the involved processes is beyond what can be
done easily with the direct data manipulation facilities available in
ddb.

Obviously this is not a completely safe thing to do, but in nearly all
cases reawakening a sleeping process is more or less harmless, plus
it's a debugger, so it seems like a worthwhile feature.

>How-To-Repeat:
n/a

>Fix:
might get to it sometime

Home	PR Database Search