From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48D763AB.3020602@domain.hid> Date: Mon, 22 Sep 2008 11:21:47 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <48D6A80F.1080206@domain.hid> <48D76206.1050609@domain.hid> In-Reply-To: <48D76206.1050609@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] Handle SIGILL when kernel compiled without Xenomai. List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai-core Jan Kiszka wrote: > Gilles Chanteperdrix wrote: >> Hi, >> >> on some (all ?) platforms, we get a SIGILL when trying to emit the first > > I don't see this on x86, though. > >> Xenomai syscall, instead of the -ENOSYS return value. This patches >> handles the SIGILL by printing an error message and exiting. >> >> Index: include/asm-generic/bits/bind.h >> =================================================================== >> --- include/asm-generic/bits/bind.h (revision 4175) >> +++ include/asm-generic/bits/bind.h (working copy) >> @@ -9,6 +9,7 @@ >> #include >> #include >> #include >> +#include >> #include >> #include >> #include >> @@ -17,6 +18,8 @@ __attribute__ ((weak)) >> pthread_key_t xeno_current_key; >> __attribute__ ((weak)) >> pthread_once_t xeno_init_current_key_once = PTHREAD_ONCE_INIT; >> +__attribute__ ((weak)) >> +jmp_buf xeno_sigill_jmpbuf; >> >> __attribute__ ((weak)) >> void xeno_set_current(void) >> @@ -99,13 +102,28 @@ static void unmap_sem_heap(unsigned long >> } >> #endif /* CONFIG_XENO_FASTSEM */ >> >> +void __attribute__((weak)) xeno_sigill_handler(int sig) >> +{ >> + siglongjmp(xeno_sigill_jmpbuf, 1); >> +} >> + > > Just one question: Can we safely assume that sigsetjmp&siglongjump are > always available, also in uclibc environments e.g.? Ok. We can use setjmp/longjmp and assume that only SIGILL is masked at the longjmp call site ? -- Gilles.