On Mon, 11 Feb 2002, Bruce Evans wrote: > On Sun, 10 Feb 2002, Daniel Eischen wrote: > > > Hmm, <sys/signal.h> includes <sys/ucontext.h>. I'm not sure why though. > > bde might know. > > <sys/signal.h> includes <machine/signal.h> for the normal namespace > pollution that was needed to use sigreturn(2) (except sigreturn(2) > itself isn't actually declared anywhere). Including <sys/ucontext.h> > gives the corresponding namespace pollution for using the current > sigreturn(2). This is probably a mistake. (Don't believe the > sigreturn man page; it documents osigreturn(2) for the i386 only.) > Programs shouldn't have any problems with this, since they should > define _POSIX_SOURCE if they only want the POSIX namespace ;-).
Poking about on a Solaris 8 system shows that they have a <ucontext.h> that defines the {get,set,make,swap}context prototypes. <ucontext.h> also includes <sys/ucontext.h> to get the definitions for ucontext_t. Under FreeBSD, <ucontext.h> is a link to <sys/ucontext.h>, which both declare ucontext_t and {get,set,make,swap}context. What do you recommend we do? Should we not include <sys/ucontext.h> from <sys/signal.h>, or do what Solaris does, or just leave everything as is? -- Dan Eischen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message