As you can see in the below image, when testapp.exe is run via Simpleator the "Hello World: 1 testapp.exe" is written to the Monitor Window but is not written to the Command Prompt window that is created via emulator.exe.
I have testapp.exe looping through printing values and if I close the Command Prompt window created by emulator.exe then the testapp.exe is no longer executing in Simpleator (non zero exit code).
I can't see where this message is coming from in the Monitor UI so assume that the incorrect process ID is used for system calls and that the process ID should be that of the child process created in emulator.exe.
Still familiarising myself with the codebase but if you could please point me in the right direction (or provide a fix if it's simple) that would be much appreciated.
As you can see in the below image, when testapp.exe is run via Simpleator the "Hello World: 1 testapp.exe" is written to the Monitor Window but is not written to the Command Prompt window that is created via emulator.exe.
I have testapp.exe looping through printing values and if I close the Command Prompt window created by emulator.exe then the testapp.exe is no longer executing in Simpleator (non zero exit code).
I can't see where this message is coming from in the Monitor UI so assume that the incorrect process ID is used for system calls and that the process ID should be that of the child process created in emulator.exe.
Still familiarising myself with the codebase but if you could please point me in the right direction (or provide a fix if it's simple) that would be much appreciated.