The testsuite you're running is segfaulting. This is not a bug in
Ubuntu, it's a bug in that testsuite. When you build the testsuite
binaries using Ubuntu's hardening-by-default compiler, buffer overflow
detection is enabled, which traps program execution immediately with
SIGSEGV.
The code of the testsuite you've pointed to has obvious and trivial
buffer overflows. The stack trace included in this report points to a
sprintf() call in conformance/interfaces/sem_unlink/1-1.c:
#define TEST "1-1"
#define FUNCTION "sem_unlink"
[...]
int main() {
[...]
char semname[20];
sprintf(semname, "/" FUNCTION "_" TEST "_%d", getpid());
[...]
The constant part of this string is '/sem_unlink_1-1_', which is 16
characters. Your target array has room for 19 characters (not counting
the terminating NUL), leaving only 3 characters for the PID.
There is absolutely no guarantee that the PID of the processes in the
test suite will fit in 3 characters. This "POSIX" test suite therefore
has undefined behavior according to the C language, which Ubuntu handles
by raising SIGSEGV.
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1557967
Title:
Semaphore tests are getting failed by signal
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1557967/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
