http://bugzilla.wpkg.org/show_bug.cgi?id=155 --- Comment #5 from Rainer Meier <r.meier at wpkg.org> 2009-04-25 01:42:34 --- Well the problem is as follows... Try executing the following command: %COMSPEC% /c start "test script" "script.cmd" While script.cmd contains the following: @echo off echo Sleeping sleep 10 echo sleepin2 >&2 As soon as the output is flushed in any case the shell forked by the "start" binary (which is supposed to exit immediately) is not closing and the parent process (wpkg) is not terminating and waiting for the shell window to be closed. If no flush is used, then the script (wpkg) terminates immediately and the cmd window closes after the sleep timeout of 10 seconds is over. A work-around is to put an explicit "exit" to the cmd script but this is not possible with all tools and is breaking compatibility. I will try to re-investigate some time this weekend to see if it can be solved or not. If not, then I will revert the flushing code keeping in mind that commands are not allowed to write a huge amount of output to STDOUT/STDERR (which is not good practice anyway). -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. |