Hi Pablo,

prometheus:2021-07-16 sven$ ./pharo --version
Pharo 9.0.0 built on Jul  6 2021 10:36:56 Compiler: 4.2.1 Compatible Apple LLVM 
11.0.3 (clang-1103.0.32.29)
Built from: ea8a3bfc - Commit: ea8a3bfc - Date: 2021-07-06 10:23:13 +0200
prometheus:2021-07-16 sven$ ./pharo Pharo.image printVersion
[version] 'Pharo9.0.0' 
'Pharo-9.0.0+build.1532.sha.e58ef49051bf06cad56a2dda174b8e091a45d5df (64 Bit)'
prometheus:2021-07-16 sven$ ./pharo Pharo.image eval "(ZdcSocketStream 
openConnectionToHostNamed: 'localhost' port: 12335) nextPut: 0; close. #foo"

I have said this before, but the VM version is incomprehensible for normal 
people, why can't it just be something like 10.1 like the rest of the world ?

Also, for mere mortals it is impossible to find out if something changed about 
the VM, let alone what, and how that all relates to specific versions.

I know that you guys have a lot of work, and we are very grateful for it, but 
this is how it looks from the outside.

Thx,

Sven

> On 19 Jul 2021, at 10:56, teso...@gmail.com wrote:
> 
> Hi, 
>    with the new VM I could not reproduce it. I think it was related with the 
> issue of the NetNameResolver.
> Which VM version are you using?
> 
> Thanks
> 
> On Sun, Jul 18, 2021 at 3:51 PM Sven Van Caekenberghe <s...@stfx.eu> wrote:
> Hi,
> 
> It seems that the following consistently crashes a recent/latest Pharo 9 
> image/vm on macOS:
> 
>   (ZdcSocketStream openConnectionToHostNamed: 'localhost' port: 12335) 
> nextPut: 0; close.
> 
> Command line, you can try it as follows:
> 
>  $ ./pharo Pharo.image eval "(ZdcSocketStream openConnectionToHostNamed: 
> 'localhost' port: 12335) nextPut: 0; close. #foo"
> 
> You can replace ZdcSocketStream by SocketStream, same result.
> 
> Before, trying to connect to a non-existing host:port resulted in a 
> ConnectionTimedOut: Cannot connect to 127.0.0.1:12335.
> 
> Now, the code just returns and the bad stream is then used as if it is OK, 
> which results in a hard crash.
> 
> Furthermore, there is no backtrace nor log.
> 
> Sven
> 
> 
> -- 
> Pablo Tesone.
> teso...@gmail.com

Reply via email to