Note: There was a bad value `sw' for the field `>Class:'.
	It was set to the default value of `sw-bug'.


>Number:         4537
>Category:       kern
>Synopsis:       linux emulator loops chewing up 100% of the cpu (netscape 4.04/linux)
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    kern-bug-people (Kernel Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Nov 18 10:20:01 1997
>Last-Modified:
>Originator:     Wolfgang Rupprecht
>Organization:
W S Rupprecht Computer Consulting, Fremont CA
>Release:        current (Nov 17, 1997)
>Environment:
System: NetBSD capsicum.wsrcc.com 1.3_ALPHA NetBSD 1.3_ALPHA (WSRCC) #1: Mon Nov 17 23:31:10 PST 1997 root@capsicum.wsrcc.com:/v/src/netbsd/current/sys/arch/i386/compile/WSRCC i386

>Description:
	when nescape-404/linux is run under the linux emulator libs
        v. 2.4 it won't exit cleanly when a ^C is sent to it.

        kdump has this to say about it:

  7860 netscape PSIG  SIGALRM caught handler=0x83c3980 mask=0x828d400 code=0x0
  7860 netscape CALL  sigreturn(0x861d3b4)
  7860 netscape RET   sigreturn JUSTRETURN
  7860 netscape PSIG  SIGALRM caught handler=0x83c3980 mask=0x828d400 code=0x0
  7860 netscape CALL  sigreturn(0x861d3b4)
  7860 netscape RET   sigreturn JUSTRETURN
  7860 netscape PSIG  SIGALRM caught handler=0x83c3980 mask=0x828d400 code=0x0
  7860 netscape CALL  sigreturn(0x861d3b4)
  7860 netscape RET   sigreturn JUSTRETURN
  7860 netscape PSIG  SIGALRM caught handler=0x83c3980 mask=0x828d400 code=0x0
  7860 netscape CALL  sigreturn(0x861d3b4)
  7860 netscape PSIG  SIGUSR1 SIG_DFL

At first glance it appears to be some sort of disagreement as to whether 
SIGALARM resets itself or not.

>How-To-Repeat:
	netscape <cr> ^C

>Fix:

    unknown.
>Audit-Trail:
>Unformatted: