>Number:         13041
>Category:       port-sparc64
>Synopsis:       a userland gdb "run" command will panic the system
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    port-sparc64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat May 26 04:59:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Martin Husemann
>Release:        May 24, 2001
>Organization:
	
>Environment:
	
System: NetBSD setting-sun.duskware.de 1.5V NetBSD 1.5V (SETTINGSUN) #0: Thu May 24 09:21:28 MEST 2001 martin@setting-sun.duskware.de:/usr/src/sys/arch/sparc64/compile/SETTINGSUN sparc64
Architecture: sparc64
Machine: sparc64
>Description:

In userland, using gdb on an arbitrary file and doing a "run" command will
lock the system with an endless stream of

pmap_page_protect: wired page pm 0x1ae20e0 va 0x40206000 not removed
vm wire count 1

on the console.

>How-To-Repeat:

Compile a vanilla "hello world" program with -g, load it into gdb and type
"run".

In case it matters (which I doubt): I'm using the 1.5Q gdb, probably from
the dwarf toolchain.

>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted: