gre-ilya/libuv
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc: clarify handle close behavior of uv_spawn (#5055)

Browse Source 
Contrary to how most handle init functions work, callers of uv_spawn
must always call uv_close, even if it returned an error.
This commit is contained in:
Ben Noordhuis 2026-03-11 22:43:01 +01:00 committed by GitHub
parent 6cdf71da80
commit d357575b2b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/src/process.rst
View File

@ -259,7 +259,8 @@ API
Initializes the process handle and starts the process. If the process is Initializes the process handle and starts the process. If the process is
successfully spawned, this function will return 0. Otherwise, the successfully spawned, this function will return 0. Otherwise, the
negative error code corresponding to the reason it couldn't spawn is negative error code corresponding to the reason it couldn't spawn is
returned. returned. Note that either way you must eventually call :c:func:`uv_close`
to close the handle again.
Possible reasons for failing to spawn would include (but not be limited to) Possible reasons for failing to spawn would include (but not be limited to)
the file to execute not existing, not having permissions to use the setuid or the file to execute not existing, not having permissions to use the setuid or