NetBSD Problem Report #58010

From www@netbsd.org  Fri Mar  8 21:43:55 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 8BADC1A923B
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  8 Mar 2024 21:43:55 +0000 (UTC)
Message-Id: <20240308214324.3F9111A923C@mollari.NetBSD.org>
Date: Fri,  8 Mar 2024 21:43:24 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: crash(8) doesn't support `mach cpu N' to examine registers/stack of other CPUs
X-Send-Pr-Version: www-1.0

>Number:         58010
>Category:       bin
>Synopsis:       crash(8) doesn't support `mach cpu N' to examine registers/stack of other CPUs
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Mar 08 21:45:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10, 9, 8, ...
>Organization:
The NetDDB Foundacrash
>Environment:
>Description:
The `mach cpu N' command in ddb lets you switch to another CPU's saved registers and stack, even if the CPU is running and they haven't been saved into the lwp state.  crash(8) is built without support for `mach cpu N', though.
>How-To-Repeat:
Try to examine another running CPU's registers and stack trace in a crash dump.
>Fix:
Yes, please!

Home	PR Database Search