Custom Query (115 matches)
Results (28 - 30 of 115)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#189 | fixed | Distribute Smalltalk/X demos in "toy" archive | ||
Description |
...and check that all demos have their dependency (BabeFish demo for instance requires SOAP). Backport this fix to 6.x.x as release date of 8.0.0 is yet unknown (will be release when it's "done"). |
|||
#188 | fixed | Missing output and garbage in the log when using Windows launcher | ||
Description |
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
smalltalk.bat -I --stopOnSIGSEGV -I --eval "Transcript showCR: 'Kuk'. (ExternalBytes address: 10 size: 10) byteAt: 1"
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 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 Version information
This happens on bleeding edge 8.0.0 64bit build. The |
|||
#186 | fixed | StX 8.0.0 crash when using workspace | ||
Description |
Don't know how to reproduce but I did the following steps: 1) from the main window open workspace 2) type Smalltalk version (with the auto-raise feature on) 3) with arrow keys scroll- and -down I'm attaching the complete log file for the session. |