On Mon, 30 Sep 2002, Juli Mallett wrote:
>
> Teh same that provides specification for queued signals - posix rts.
hey that's MY typo... get your own! :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
[ Subjecte: Re: signal changes ]
>
>
> On Mon, 30 Sep 2002, Juli Mallett wrote:
>
> > * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> > [ Subjecte: Re: signal change
On Mon, 30 Sep 2002, Juli Mallett wrote:
> * De: Julian Elischer <[EMAIL PROTECTED]> [ Data: 2002-09-30 ]
> [ Subjecte: Re: signal changes ]
> >
> > On Mon, 30 Sep 2002, Juli Mallett wrote:
> >
> > > > What limits are the on the number of si
Peter Wemm wrote:
>
> Before getting too far here, can we consider some other standard interfaces?
>
> #include
>
> int getcontext(ucontext_t *ucp);
> int setcontext(const ucontext_t *ucp);
> void makecontext(ucontext_t *ucp, (void *func)(), int argc, ...);
> int swapc
Marcel Moolenaar wrote:
> Garrett Wollman wrote:
> >
> > < said
:
> >
> > > The setjump/longjump family of functions are userland function
> > > AFAICT.
> >
> > POSIX doesn't make any such distinction. Remember that setjmp/longjmp
> > *already* enter the kernel, in order to save/restore th
Garrett Wollman wrote:
>
> < said:
>
> > The setjump/longjump family of functions are userland function
> > AFAICT.
>
> POSIX doesn't make any such distinction. Remember that setjmp/longjmp
> *already* enter the kernel, in order to save/restore the signal mask,
> so there isn't any real perfor
