>Number:         4117
>Category:       lib
>Synopsis:       [dM] sigaltstack(2) uses wrong names
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    lib-bug-people (Library Bug People)
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 16 14:35:02 1997
>Last-Modified:
>Originator:     der Mouse
>Organization:
	Dis-
>Release:        $NetBSD: sigaltstack.2,v 1.4 1997/03/08 13:47:08 mouse Exp $
>Environment:
	Any
>Description:
	sigaltstack(2) calls the ss_flags bits SA_ONSTACK and
	SA_DISABLE.  UTSLing reveals that they are actually SS_ONSTACK
	and SS_DISABLE; to make things more confusing, SA_ONSTACK
	actually exists (with the same value, fortunately or
	unfortunately, depending on your point of view).
>How-To-Repeat:
	Try to write code based on "man 2 sigaltstack" and get confused
	at the errors. :-)
>Fix:
	--- sigaltstack.2.OLD	Tue Sep 16 17:15:19 1997
	+++ sigaltstack.2	Tue Sep 16 17:15:47 1997
	@@ -73,7 +73,7 @@	
	 duration of the signal handler's execution. 
	 .Pp
	 If
	-.Dv SA_DISABLE
	+.Dv SS_DISABLE
	 is set in
	 .Fa ss_flags ,
	 .Fa ss_sp
	@@ -97,9 +97,9 @@
	 The
	 .Fa ss_flags
	 field will contain the value
	-.Dv SA_ONSTACK
	+.Dv SS_ONSTACK
	 if the process is currently on a signal stack and
	-.Dv SA_DISABLE
	+.Dv SS_DISABLE
	 if the signal stack is currently disabled.
	 .Sh NOTES
	 The value

					der Mouse

			       mouse@rodents.montreal.qc.ca
		     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>Audit-Trail:
>Unformatted: