Repository navigation
Unable to obtain target process exit code on Linux/Mac with CoreCLR debugging services #43731
Description
Activity
same problem was in netcoredbg
cc @kfrolov @viewizardYes, we also faced with this issue and temporary added hook for
waitpidin netcoredbg code - https://github.com/Samsung/netcoredbg/blob/0809b8aa1a80c88b35a04106fbfeb9f5be42853e/src/debugger/manageddebugger.cpp#L41-L127Due to lack of recent activity, this issue has been marked as a candidate for backlog cleanup. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will undo this process.
This process is part of our issue cleanup automation.
This issue will now be closed since it had been marked
no-recent-activitybut received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.- locked and limited conversation to collaborators
on Oct 26, 2025
Description
On Linux/Mac the exit code of the target process is obtained through waitpid (Linux docs, Apple docs, PAL code that makes use of it). However, unlike on Windows -- if multiple places in a process are calling waitpid, unless the
WNOWAITflag is used (which doesn't seem to exist OSX), then my understanding is that this will prevent other callers from obtaining the exit code.The debugging services open a HANDLE to the target process (as expected) through the PAL, which means that they may wind up 'owning' the exit code of the target process, but they don't, at least as far as I know, wind up propagating this exit code to the debugger.
The potential fixes I can think of are:
-or-
Regression?
No, this has never worked on Linux/Mac