summaryrefslogtreecommitdiff
path: root/libguile/scmsigs.c
diff options
context:
space:
mode:
authorAndrea Azzarone <andrea.azzarone@canonical.com>2019-04-11 16:30:58 +0100
committerMark H Weaver <mhw@netris.org>2019-04-16 16:54:55 -0400
commit546b0e87294b837ec29164d87cf17102e9aeee0c (patch)
treedb9f8891b995a462d5ad4c62ccea2f80e9086b66 /libguile/scmsigs.c
parent423ad3632f474461a49706f5dd20518ca0efc31f (diff)
downloadguile-546b0e87294b837ec29164d87cf17102e9aeee0c.tar.gz
Fix gc.test "after-gc-hook gets called" failures.
* libguile/scmsigs.c (signal_delivery_thread): Call scm_async_tick to give any pending asyncs a chance to run before we block indefinitely waiting for a signal to arrive.
Diffstat (limited to 'libguile/scmsigs.c')
-rw-r--r--libguile/scmsigs.c8
1 files changed, 8 insertions, 0 deletions
diff --git a/libguile/scmsigs.c b/libguile/scmsigs.c
index 21b2a9529..755e657ea 100644
--- a/libguile/scmsigs.c
+++ b/libguile/scmsigs.c
@@ -174,6 +174,14 @@ signal_delivery_thread (void *data)
{
struct signal_pipe_data sigdata;
+ /* This tick gives any pending asyncs a chance to run before we
+ block indefinitely waiting for a signal to arrive. For example
+ it can happen that the garbage collector is triggered while
+ marking the signal handler for future execution. Due to the
+ way the after-gc-hook is designed, without a call to
+ scm_async_tick, the after-gc-hook will not be triggered. */
+ scm_async_tick ();
+
scm_without_guile (read_signal_pipe_data, &sigdata);
sig = sigdata.sigbyte;