[systemd-bugs] [Bug 84931] New: systemd --test: Assertion 'sigaddset(ss, sig) == 0' failed at .../work/systemd-206/src/shared/util.c:2516, function sigset_add_many(). Aborting
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Oct 12 02:56:31 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=84931
Bug ID: 84931
Summary: systemd --test: Assertion 'sigaddset(ss, sig) == 0'
failed at .../work/systemd-206/src/shared/util.c:2516,
function sigset_add_many(). Aborting
Product: systemd
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: pachoramos1 at gmail.com
QA Contact: systemd-bugs at lists.freedesktop.org
Hello
Long time ago the following test failure was reported downstream to:
https://bugs.gentoo.org/show_bug.cgi?id=482214
It affects to HPPA but, as our main hppa developer thinks systemd upstream
wouldn't be too cooperative to fix this, he still didn't report it (even if the
issue still occurs with newer versions):
$ /bin/systemd --test
Assertion 'sigaddset(ss, sig) == 0' failed at
/var/tmp/portage/sys-apps/systemd-206-r3/work/systemd-206/src/shared/util.c:2516,
function sigset_add_many(). Aborting.
Aborted
The following information could help you to try to find the problem:
"I'm pretty sure the problem arises in src/core/manager.c:411
#include <stdio.h>
#include <signal.h>
int main( int argc,char * argv )
{
printf("%d\n", SIGRTMIN);
}
# ./SIGRTMIN
39
systemd is adding SIGRTMIN+29 (which is well over SIGRTMAX) and isn't checking
that properly[1].
[1] signal(7): "include suitable (run-time) checks that SIGRT‐MIN+n does not
exceed SIGRTMAX"
On PARISC, we have:
#define SIGXCPU 33
#define SIGXFSZ 34
#define SIGSTKFLT 36
and it has been like this since the initial Linux port, it seems. I can't find
historical information on this choice.
37 is the first available real-time signal, to which glibc adds another 2 for
NPTL, so 39 is the first available signal.
"
Not sure if you would know how to handle this :/
Thanks a lot
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20141012/2eb32d91/attachment.html>
More information about the systemd-bugs
mailing list