id,summary,reporter,owner,description,type,status,priority,milestone,component,resolution,keywords,cc,cvshead 188,Missing output and garbage in the log when using Windows launcher,jan vrany,patrik.svestka@…,"I'm experiencing weird behavior of the launcher, sometimes not showing me the output on the console and writing a garbage to the log file: **Steps to reproduce** 1. Run following command: {{{ smalltalk.bat -I --stopOnSIGSEGV -I --eval ""Transcript showCR: 'Kuk'. (ExternalBytes address: 10 size: 10) byteAt: 1"" }}} 2. Kill the `stx.com` process after some time, 5 mins should be safe. **Observed behavior** Until killed, the console output is the following: {{{ ""[INFO] PowerShell detected: ->TRUE<-. ""[INFO] The latest latest_powershell_version found: 2.0."" ""[INFO] With the runtime being: v2.0.50727."" VERBOSE: [INFO] No log file found turning off the append mode. VERBOSE: VERBOSE: [INFO] Executing command: H:\Projects\SmalltalkX\sources\stx_8_0_0\build\stx\projects\smalltalk\stx.com ""--stopOnSIGSEGV"" ""-I"" ""--quick"" ""--eval"" ""Transcript showCR: 'Kuk'. (ExternalBytes address: 10 size: 10) byteAt: 1"" 2>&1 | Tee-Host | Out-File -Encoding UTF8 -FilePath H:\Projects\SmalltalkX\sources\stx_8_0_0\build\stx\projects\smalltalk\smalltalk_2017-12-19_utf8.log -Width 150 VERBOSE: Kuk }}} Then, when killed, it shows: {{{ [ERROR] happned in PowerShell (can be also stx.com) - See log file: H:\Projects\SmalltalkX\sources\stx_8_0_0\build\stx\projects\smalltalk\smallta lk_2017-12-19_utf8.log. VERBOSE: VERBOSE: [INFO] Exiting from PowerShell with code 1 }}} The contents of the `.log` file is attached. Note the Powershell error and garbage at the end - actually it's an UTF16 text. Also note, that the information about the segmentation violation shown by the VM is missing completely (se below what I'd expect). **Expected behavior** Running the very same command without launcher produces following output on the console (before it is killed): {{{ > stx --stopOnSIGSEGV -I --quick --eval ""Transcript showCR: 'Kuk'. (ExternalBytes address: 10 size: 10) byteAt: 1"" Kuk VM [sigsegv]: sigNo 11 context=6caab08 sp=6caaa70 VM [error] (17-12-19 22:08:05): Got SEGV, stopping for debugger to attach error occured (see above), waiting 30 mins for debugger to attach to terminate: taskkill /F /PID 1564 to attach a debugger: gdb attach 1564 }}} When using launcher, I'd expect this text to be shown in the console and as well in the `.log` file. **Version information** This happens on bleeding edge 8.0.0 64bit build. The `stx:projects/smalltalk` package revision is `09e37fd93f8f`, the working copy is clean, `smalltalk.cfg` unmodified. ",defect,closed,major,8.0.0,default,fixed,,patrik.svestka@…,0