On Sun, May 17, 2015 at 10:49:23PM +0200, Daniel Golle wrote:
> uClibc doesn't define signal info for the SIGSYS signal which is issued
> in case of hitting a syscall prohibited by seccomp.
> This is sad as it makes debugging seccomp filter policies impossible on
> some architectures (at least ARM and PowerPC, maybe also others) which
> do not coincidentally set si_value.sival_int as the syscall number.
> 
> To fix this, import the definitions and macros needed from glibc.

Applied, thanks!
_______________________________________________
uClibc mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/uclibc

Reply via email to