<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - systemd --test: Assertion 'sigaddset(ss, sig) == 0' failed at .../work/systemd-206/src/shared/util.c:2516, function sigset_add_many(). Aborting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84931">84931</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd --test: Assertion 'sigaddset(ss, sig) == 0' failed at .../work/systemd-206/src/shared/util.c:2516, function sigset_add_many(). Aborting
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>pachoramos1@gmail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Hello
Long time ago the following test failure was reported downstream to:
<a href="https://bugs.gentoo.org/show_bug.cgi?id=482214">https://bugs.gentoo.org/show_bug.cgi?id=482214</a>
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</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>