[lkml]   [1996]   [May]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: SA_STACK
>  OK, I've found an SVR4 box here that I can log-on to (I'm a contractor
> here, and only just found out they had such a beast).
> It's an DGUX 5.4R3.10, and I've normally found that DG are pretty
> 2) setjmp() and sigsetjmp() do _not_ store the current stack, or
> if they do, longjmp() and siglongjmp() ignore it. When in a
> signal handler, running on an alt-stack, performs a *longjmp()
> the process continues running on the alt-stack (at least a call
> to altsigstack() reports the alt-stack is in use). You were
> right, this is wrong - simply returning from a function after a
> *longjmp() causes a core dump!!!!

Hmm, according to libc source, bp and sp are saved. So I would assume
Linux setjmp()/longjmp() work like the DGUX setcontext()/getcontext() ?
What is the desireable action? Even in the semantics of setjmp()/longjmp()
you HAVE to store/restore stack or it is pretty useless.

> If you're *setjmp()/*longjmp() routines are working correctly with
> alt-stacks, congradulations(sp?). I'm still v. much in favour of
> having a get/setcontext(), but that's probably just me...

Seems that maybe DGUX does it wrong?


 \ /
  Last update: 2005-03-22 13:37    [W:0.039 / U:1.512 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site