diff options
| author | Simon McVittie <smcv@collabora.com> | 2021-06-14 13:06:51 +0100 |
|---|---|---|
| committer | Simon McVittie <smcv@collabora.com> | 2021-06-15 14:33:17 +0100 |
| commit | b483013d020091762b7182127e3cbf9e6c3f43de (patch) | |
| tree | 122b8b07bcbf13aedaa7ff7781c3ab06641c04ac | |
| parent | e0b6b8037d49adb5096f1ba584c80e58686a367a (diff) | |
| download | glib-b483013d020091762b7182127e3cbf9e6c3f43de.tar.gz | |
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 <smcv@collabora.com>
| -rw-r--r-- | glib/gspawn.c | 4 |
1 files 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 |