https://bugs.winehq.org/show_bug.cgi?id=57804
Bug ID: 57804 Summary: cmd: CALL instruction freezes Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: cmd Assignee: wine-bugs@winehq.org Reporter: Dominik-Home@gmx.de Distribution: ---
Executing the 'CALL'-instruction on a *.bat file may causes freezes when using e.g. '@echo off' in the called script.
```console $ wine --version wine-10.0 (Staging) ```
I inserted two minimal reproducers below that are used in the following examples. Note that I marked the output of the scripts as comment with the REM command as well as my own descriptions.
```cmd C:>C:\working.bat REM C:>echo Test REM Test REM Command returns immediately. No issue here
C:>C:\issue.bat REM Test REM Command returns immediately. No issue here
C:>CALL C:\working.bat REM C:>echo Test REM Test REM Command returns immediately. No issue here
C:>CALL C:\issue.bat REM Test REM ISSUE: Command freezes here and never returns ```
working.bat: ```cmd @echo on
echo Test ```
issue.bat: ```cmd @echo off
echo Test ```
This issue was encountered while trying out PlanAhead, a tool included in the Xilinx ISE design package. They use multiple batch scripts to configure the environment before starting the GUI application. Because the batch files do not work properly the GUI does not start at all. I.e. the application (PlanAhead) is completely unusable.