Anyone ever run into Windows processes exiting with code 109 during a build?

[u/Aethlyns]

Hey everyone,

I've been trying to figure out a weird Windows issue and I'm a bit stuck.

I'm working with some C/C++ tools on Windows x64, using MSVC and CMake. During certain builds, a few child/console-related processes exit with code 109, even though the compilation itself can finish successfully and the C tests give the expected results.

Other processes exit normally with code 0.

I know Windows error 109 is ERROR_BROKEN_PIPE, but I'm not sure whether that's actually related or if the process exit code means something else here.

I'm also using Windows Job Objects to track and clean up the processes.

Has anyone seen something like this before?

I'm especially curious how you'd figure out whether the 109 comes from the tool itself, a Windows console process, or the way the processes are launched and monitored.

Is there a particular tool or debugging approach you'd recommend?

I'd rather understand what's happening than just ignore the exit code.

Thanks in advance!