>Number:         11126
>Category:       port-sparc
>Synopsis:       kgdb client (target) mode on sparc causes crash
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    port-sparc-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 03 17:49:00 PDT 2000
>Closed-Date:
>Last-Modified:
>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: