Messages in this thread | ![/](/images/icornerl.gif) | | Date | Wed, 5 Nov 2003 09:11:44 +0100 | From | Alex Riesen <> | Subject | Re: K 2.6 test6 strange signal behaviour |
| |
Ken Foskey, Tue, Oct 21, 2003 03:56:10 +0200: > On Tue, 2003-10-21 at 06:28, Andrew Morton wrote: > > Ken Foskey <foskey@optushome.com.au> wrote: > > > > > > I have a problem with signals. > > > > You should be using sigsetjmp(), not setjmp(). > > No difference. Note that this is K 2.6 specific, it "works" in K 2.4. > > I am reading on sigaction now, I will recode with SA_RESTART tonight.
recode it with SA_NOMASK (and please, remove all that forest around the code if you post it here).
Can someone explain here, how exactly setjmp/longjmp breaks expected behaviour?
> I think this is not the solution because I am explicitly setting the > signal handler before every call. I think this simply leaves the signal > handler active ie old BSD style.
no. See the glibc source, posix/signal.c
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| ![\](/images/icornerr.gif) |