Hi, I have an application that uses seccomp in strict mode. When the application is finished, it uses the _exit(2) system call to terminate, as documented in seccomp(2). glibc however uses NR_exit_group, which is a seccomp violation, so the process is ended with SIGKILL instead. Simon
Hi, Yes, glibc does that since version 2.3 in order to terminate all threads. I fail to see why it's a glibc issue though, this looks like more a seccomp decision to not allow this syscall in strict mode. Regards Aurelien
reassign 1134384 manpages-dev retitle 1134384 Document _exit(2) pitfall with seccomp(2) tags 1134384 +patch found 6.9.1-1 thanks I guess the most sensible thing we can do here is document it. Simon