NetBSD Problem Report #11126

Received: (qmail 4485 invoked from network); 4 Oct 2000 00:48:33 -0000
Message-Id: <200010040048.LAA18366@mundamutti.cs.mu.OZ.AU>
Date: Wed, 4 Oct 2000 11:48:29 +1100 (EST)
From: kre@munnari.OZ.AU
Reply-To: kre@munnari.OZ.AU
To: gnats-bugs@gnats.netbsd.org
Subject: kgdb fails on sparc
X-Send-Pr-Version: 3.95

>Number:         11126
>Category:       port-sparc
>Synopsis:       kgdb client (target) mode on sparc causes panic
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Oct 04 00:49:00 +0000 2000
>Closed-Date:    
>Last-Modified:  Sat Nov 12 16:02:23 +0000 2005
>Originator:     Robert Elz
>Release:        NetBSD 1.3H
>Organization:
University of Melbourne
>Environment:

System: NetBSD copenhagen.cs.mu.OZ.AU 1.3H NetBSD 1.3H (CompSci-IPX) #4: Mon Sep 7 03:44:40 EST 1998 root@dublin.cs.mu.OZ.AU:/local/netbsd/src/sys/arch/sparc/compile/CompSci-IPX sparc


>Description:
	Continuing from a breakpoint (or other halt) on a kgdb client
	sparc causes almost immediate panic - seemingly caused by a
	register (or registers) not being properly saved/restored
	during the kgdb exchange with the controlling system.
>How-To-Repeat:
	Simply setup and run kgdb on a sparc (4c if it matters, IPX), cause
	the controller to connect to the target (which stops the target),
	tell the target to continue - observe panic.   Happens reliably when
	the target was otherwise just sitting in its idle loop.
>Fix:
	Don't use kgdb on sparc.

	Note - this is a very late report of a problem observed (it seems
	from the date of the kernel that is running) more than 2 years ago.
	I don't recall seeing any change notifications with comments that
	would suggest this has been fixed - but 2 years is a long time.
>Release-Note:
>Audit-Trail:
>Unformatted:

Home	PR Database Search