Re: sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

Nicholas Miell wrote: > so if uc_stack doesn't point to the stack in use immediately prior to > signal generation, this is a bug. Looking at arch/i386/kernel/signal.c (and others) inside setup_rt_frame(), the problem is pretty obvious: err |= __put_user(current->sas_ss_sp,

Re: sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

Nicholas Miell wrote: so if uc_stack doesn't point to the stack in use immediately prior to signal generation, this is a bug. Looking at arch/i386/kernel/signal.c (and others) inside setup_rt_frame(), the problem is pretty obvious: err |= __put_user(current-sas_ss_sp,

Re: sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

On Mon, 2007-01-22 at 09:57 +0100, Xavier Roche wrote: > Hi folks, > > I have a probably louzy question regarding sigaction() behaviour when an > alternate signal stack is used: it seems that I can not get the user > stack reference in the ucontext_t stack context ; ie. the uc_stack > member

sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

Hi folks, I have a probably louzy question regarding sigaction() behaviour when an alternate signal stack is used: it seems that I can not get the user stack reference in the ucontext_t stack context ; ie. the uc_stack member contains reference of the alternate signal stack, not the stack that

sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

Hi folks, I have a probably louzy question regarding sigaction() behaviour when an alternate signal stack is used: it seems that I can not get the user stack reference in the ucontext_t stack context ; ie. the uc_stack member contains reference of the alternate signal stack, not the stack that

Re: sigaction's ucontext_t with incorrect stack reference when SA_SIGINFO is being used ?

On Mon, 2007-01-22 at 09:57 +0100, Xavier Roche wrote: Hi folks, I have a probably louzy question regarding sigaction() behaviour when an alternate signal stack is used: it seems that I can not get the user stack reference in the ucontext_t stack context ; ie. the uc_stack member contains