ehmry/genode
ehmry
/
genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

core-linux: avoid block-for-signal assertion 

This patch removes the assertion about the unexpected call of
'block_for_signal' within core. On Linux, this call is actually
expected because of the handling of SIGCHLD signals by core.
This commit is contained in:
Norman Feske 2017-08-18 12:50:33 +02:00 committed by Christian Helmuth
parent 94f428a8b6
commit 556fec24b1
1 changed files with 15 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
repos/base/src/core/signal_receiver.cc
View File

@ -16,6 +16,7 @@
/* Genode includes */
#include <base/env.h>
#include <base/sleep.h>
/* base-internal includes */
#include <base/internal/globals.h>
@ -35,6 +36,17 @@ void Signal_receiver::unblock_signal_waiter(Rpc_entrypoint &) { ASSERT_NEVER_CAL
typedef Signal_context_capability Sigh_cap;
Sigh_cap Signal_receiver::manage(Signal_context *) { ASSERT_NEVER_CALLED; }
void Signal_receiver::block_for_signal() { ASSERT_NEVER_CALLED; }
void Signal_receiver::local_submit(Signal::Data) { ASSERT_NEVER_CALLED; }
Sigh_cap Signal_receiver::manage(Signal_context *) { ASSERT_NEVER_CALLED; }
void Signal_receiver::block_for_signal()
{
/*
* Called by 'entrypoint.cc' after leaving the 'Rpc_construct' RPC call.
* This happens in particular when the blocking for the reply for the
* 'Rpc_construct' call is canceled by an incoming SIGCHLD signal, which
* occurs whenever a child component exits.
*/
sleep_forever();
}
void Signal_receiver::local_submit(Signal::Data) { ASSERT_NEVER_CALLED; }