From b483013d020091762b7182127e3cbf9e6c3f43de Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Mon, 14 Jun 2021 13:06:51 +0100 Subject: [PATCH] spawn: Clarify the most common non-exit reason for process termination A reader might think "how would a process terminate without an exit status?", or equivalently, "what harm would it do if I assume every termination has an exit status?" without this reminder that termination with a signal is also reasonably common. Signed-off-by: Simon McVittie --- glib/gspawn.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/glib/gspawn.c b/glib/gspawn.c index dd2972f83..899647c2f 100644 --- a/glib/gspawn.c +++ b/glib/gspawn.c @@ -1121,8 +1121,8 @@ g_spawn_command_line_async (const gchar *command_line, * This allows you to differentiate between different exit codes. * * If the process was terminated by some means other than an exit - * status, the domain will be %G_SPAWN_ERROR, and the code will be - * %G_SPAWN_ERROR_FAILED. + * status (for example if it was killed by a signal), the domain will be + * %G_SPAWN_ERROR and the code will be %G_SPAWN_ERROR_FAILED. * * This function just offers convenience; you can of course also check * the available platform via a macro such as %G_OS_UNIX, and use