At Tue, 31 Oct 2023 18:11:48 +0530, vignesh C <vignes...@gmail.com> wrote in > Few others are also facing this problem with similar code like in: > https://stackoverflow.com/questions/15882799/fgets-returning-error-for-file-returned-by-popen
I'm inclined to believe that the pipe won't enter the EOF state until the target command terminates (then the top-level cmd.exe). The target command likely terminated prematurely due to an error before priting any output. If we append "2>&1" to the command line, we can capture the error message through the returned pipe if any. Such error messages will cause the subsequent code to fail with an error such as "unexpected string: 'the output'". I'm not sure, but if this is permissive, the returned error messages could potentially provide insight into the underlying issue, paving the way for a potential solution. regards. -- Kyotaro Horiguchi NTT Open Source Software Center
