aboutsummaryrefslogtreecommitdiffstats
path: root/prototypes/connections/test-async.c
diff options
context:
space:
mode:
authoreunhhu <[email protected]>2026-10-01 16:40:11 +0100
committereunhhu <[email protected]>2026-10-01 16:40:11 +0100
commit1fdf72444cdcf5041022c75ed616a1dcd458175b (patch)
tree73e1c333f2a1a1867db18bb346172f054bdf2912 /prototypes/connections/test-async.c
parent2963fb5a7deb0cca24c3aa410a11ebc0f8fb559a (diff)
downloadpure-1fdf72444cdcf5041022c75ed616a1dcd458175b.tar.gz
pure-1fdf72444cdcf5041022c75ed616a1dcd458175b.zip
Look at a wake write's result in the prototype, as fortified builds ask
Ubuntu's gcc defines _FORTIFY_SOURCE, which marks write's result as one to use, and a (void) cast does not quiet it: the prototype did not build there (research 029). Debian's does not define it; the Pi gives the same error with -D_FORTIFY_SOURCE=3.
Diffstat (limited to 'prototypes/connections/test-async.c')
-rw-r--r--prototypes/connections/test-async.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/prototypes/connections/test-async.c b/prototypes/connections/test-async.c
index ad5f15a..e31b1d7 100644
--- a/prototypes/connections/test-async.c
+++ b/prototypes/connections/test-async.c
@@ -38,7 +38,7 @@ static void *write_after_signal(void *context) {
worker->effect.value, &worker->reply,
&worker->revision);
}
- (void)write(worker->done, &byte, 1);
+ if (write(worker->done, &byte, 1) < 0) { /* full: its reader is woken already */ }
return NULL;
}