[wpkg-users] [Bug 155] stdout/stderr flush code causes some commands to hang

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=155





--- Comment #10 from Rainer Meier <r.meier at wpkg.org>  2009-05-27 21:33:29 ---
It might be correct that there is no clean work-around for this problem. I am
thinking about removing the work-around completely and just live with the fact
that called programs should not print > 4k of output to STDOUT/STDERR or they
might be blocked.
For most applications this is not a problem since installers usually don't
print to STDOUT/STDERR. If really necessary the command might be embedded into
a custom %COMSPEC% coammand which redirects the output to a file or /dev/null.

Let's see if somebody comes up with a working solution (I will have a closer
look too) but if there is no solution we will mark this as a "known bug".
Unfortunately Microsoft seems not to be interested in maintaining
cscript/wscript and they will not fix this problem.

-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.