<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c1">Comment # 1</a>
on <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">bug 84931</a>
from <span class="vcard"><a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> <span class="fn">Lennart Poettering</span></a>
</span></b>
<pre>Hmm, did I get this right? SIGRTMAX-SIGRTMIN is different for Linux on hppa
than for Linux on all other archs?
Yuck, what a fuck-up.
The only sane solution I see is adding a patch that #ifdefs out the code that
binds to the high SIGRTMIN+n signals.
What's the last SIGRTMIN+n that works on hppa? Or in other words, what is
SIGRTMAX-SIGRTMIN? If you let me know we'll just skip all signal assignments
beyond this value on #ifdef __hppa__
Note that the signals we expose are kinda API, hence we cannot dynamically
assign them. Hence checking things against SIGRTMAX and shifting things around
is really not a good idea. And normally this wouldn't be a problem as on
Linux/glibc the number of rt sigs should be stable and fixed. Apparently though
with the exception of Linux/hppa...</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>