A problem with latest image (64bit) ? (Please confirm)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

A problem with latest image (64bit) ? (Please confirm)

EstebanLM
Hello,

I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
After doing

Stdio stdout << ‘OK’

I’m having this stack:

File class(ProtoObject)>>primitiveFailed:
File class(ProtoObject)>>primitiveFailed
File class>>fileDescriptorType:
File class>>fileDescriptorIsAvailable:
Stdio class>>standardIOStreamNamed:forWrite:
Stdio class>>stdout
UndefinedObject>>DoIt
OpalCompiler>>evaluate
RubSmalltalkEditor>>evaluate:andDo:
RubSmalltalkEditor>>highlightEvaluateAndDo:
GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
MorphicAlarm(MessageSend)>>value
MorphicAlarm>>value:
WorldState>>triggerAlarmsBefore:
WorldState>>runLocalStepMethodsIn:
WorldState>>runStepMethodsIn:
WorldMorph>>runStepMethods
WorldState>>doOneCycleNowFor:
WorldState>>doOneCycleFor:
WorldMorph>>doOneCycle
WorldMorph class>>doOneCycle
[ [ WorldMorph doOneCycle.
Processor yield.
false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....
[ self value.
Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....

Con someone confirm or refute this?

Thanks!
Esteban
Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

gcotelli
At least on Linux (with the latest VM and image downloaded for zero conf) it's working fine.

Image
-----
Pharo7.0.0rc1
Build information: Pharo-7.0.0+rc1.build.121.sha.0640e0d300e69541033fb1c4270c9b0d7d401b01 (64 Bit)
Unnamed

Virtual Machine
---------------
pharo-vm/lib/pharo/5.0-201901100922/pharo
CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019
VM: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jan 10 10:22:25 2019 CommitHash: 58ffe032 Plugins: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git

Unix built on Jan 10 2019 09:32:18 Compiler: 4.8.4
VMMaker versionString VM: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jan 10 10:22:25 2019 CommitHash: 58ffe032 Plugins: 201901100922 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
CoInterpreter VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid: a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan 10 2019

Operating System/Hardware
-------------------------
unix linux-gnu x86_64




On Tue, Jan 15, 2019 at 8:31 AM Esteban Lorenzano <[hidden email]> wrote:
Hello,

I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
After doing

Stdio stdout << ‘OK’

I’m having this stack:

File class(ProtoObject)>>primitiveFailed:
File class(ProtoObject)>>primitiveFailed
File class>>fileDescriptorType:
File class>>fileDescriptorIsAvailable:
Stdio class>>standardIOStreamNamed:forWrite:
Stdio class>>stdout
UndefinedObject>>DoIt
OpalCompiler>>evaluate
RubSmalltalkEditor>>evaluate:andDo:
RubSmalltalkEditor>>highlightEvaluateAndDo:
GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
MorphicAlarm(MessageSend)>>value
MorphicAlarm>>value:
WorldState>>triggerAlarmsBefore:
WorldState>>runLocalStepMethodsIn:
WorldState>>runStepMethodsIn:
WorldMorph>>runStepMethods
WorldState>>doOneCycleNowFor:
WorldState>>doOneCycleFor:
WorldMorph>>doOneCycle
WorldMorph class>>doOneCycle
[ [ WorldMorph doOneCycle.
Processor yield.
false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....
[ self value.
Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....

Con someone confirm or refute this?

Thanks!
Esteban
Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

Max Leske
In reply to this post by EstebanLM
I've been seeing this in the early Pharo 7 builds. But it didn't occur
with latest VM's, only with SmalltalkCI, so I ignored it.

On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:

> Hello,
>
> I’m experiencing a problem with latest image (and latest vm) in Mac
> (Mojave).
> After doing
>
> Stdio stdout << ‘OK’
>
> I’m having this stack:
>
> File class(ProtoObject)>>primitiveFailed:
> File class(ProtoObject)>>primitiveFailed
> File class>>fileDescriptorType:
> File class>>fileDescriptorIsAvailable:
> Stdio class>>standardIOStreamNamed:forWrite:
> Stdio class>>stdout
> UndefinedObject>>DoIt
> OpalCompiler>>evaluate
> RubSmalltalkEditor>>evaluate:andDo:
> RubSmalltalkEditor>>highlightEvaluateAndDo:
> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
> MorphicAlarm(MessageSend)>>value
> MorphicAlarm>>value:
> WorldState>>triggerAlarmsBefore:
> WorldState>>runLocalStepMethodsIn:
> WorldState>>runStepMethodsIn:
> WorldMorph>>runStepMethods
> WorldState>>doOneCycleNowFor:
> WorldState>>doOneCycleFor:
> WorldMorph>>doOneCycle
> WorldMorph class>>doOneCycle
> [ [ WorldMorph doOneCycle.
> Processor yield.
> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in
> Block: [ [ WorldMorph doOneCycle....
> [ self value.
> Processor terminateActive ] in BlockClosure>>newProcess in Block: [
> self value....
>
> Con someone confirm or refute this?
>
> Thanks!
> Esteban

Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

Max Leske
In reply to this post by EstebanLM
Actually, I think it's rather a VM problem...?


On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:

> Hello,
>
> I’m experiencing a problem with latest image (and latest vm) in Mac
> (Mojave).
> After doing
>
> Stdio stdout << ‘OK’
>
> I’m having this stack:
>
> File class(ProtoObject)>>primitiveFailed:
> File class(ProtoObject)>>primitiveFailed
> File class>>fileDescriptorType:
> File class>>fileDescriptorIsAvailable:
> Stdio class>>standardIOStreamNamed:forWrite:
> Stdio class>>stdout
> UndefinedObject>>DoIt
> OpalCompiler>>evaluate
> RubSmalltalkEditor>>evaluate:andDo:
> RubSmalltalkEditor>>highlightEvaluateAndDo:
> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
> MorphicAlarm(MessageSend)>>value
> MorphicAlarm>>value:
> WorldState>>triggerAlarmsBefore:
> WorldState>>runLocalStepMethodsIn:
> WorldState>>runStepMethodsIn:
> WorldMorph>>runStepMethods
> WorldState>>doOneCycleNowFor:
> WorldState>>doOneCycleFor:
> WorldMorph>>doOneCycle
> WorldMorph class>>doOneCycle
> [ [ WorldMorph doOneCycle.
> Processor yield.
> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in
> Block: [ [ WorldMorph doOneCycle....
> [ self value.
> Processor terminateActive ] in BlockClosure>>newProcess in Block: [
> self value....
>
> Con someone confirm or refute this?
>
> Thanks!
> Esteban

Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

EstebanLM
Thing is, it happens also with an older VM :(

Esteban

> On 15 Jan 2019, at 13:00, Max Leske <[hidden email]> wrote:
>
> Actually, I think it's rather a VM problem...?
>
>
> On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:
>
>> Hello,
>>
>> I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
>> After doing
>>
>> Stdio stdout << ‘OK’
>>
>> I’m having this stack:
>>
>> File class(ProtoObject)>>primitiveFailed:
>> File class(ProtoObject)>>primitiveFailed
>> File class>>fileDescriptorType:
>> File class>>fileDescriptorIsAvailable:
>> Stdio class>>standardIOStreamNamed:forWrite:
>> Stdio class>>stdout
>> UndefinedObject>>DoIt
>> OpalCompiler>>evaluate
>> RubSmalltalkEditor>>evaluate:andDo:
>> RubSmalltalkEditor>>highlightEvaluateAndDo:
>> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
>> MorphicAlarm(MessageSend)>>value
>> MorphicAlarm>>value:
>> WorldState>>triggerAlarmsBefore:
>> WorldState>>runLocalStepMethodsIn:
>> WorldState>>runStepMethodsIn:
>> WorldMorph>>runStepMethods
>> WorldState>>doOneCycleNowFor:
>> WorldState>>doOneCycleFor:
>> WorldMorph>>doOneCycle
>> WorldMorph class>>doOneCycle
>> [ [ WorldMorph doOneCycle.
>> Processor yield.
>> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....
>> [ self value.
>> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....
>>
>> Con someone confirm or refute this?
>>
>> Thanks!
>> Esteban
>


Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

tinchodias
Hi,
I iouldn't reproduce in macos mojave. I downloaded with:

curl https://get.pharo.org/64/70+vmLatest | bash

And no problem with

Stdio stdout << ‘OK’

Report:

---
Pharo7.0.0rc1
Build information:
Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885
(64 Bit)
Unnamed

CoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins:
201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git

Mac OS X built on Jan  5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible
Apple LLVM 7.3.0 (clang-703.0.31)
VMMaker versionString VM: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5
20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
https://github.com/OpenSmalltalk/opensmalltalk-vm.git
CoInterpreter VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
---

Martín


El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano
([hidden email]) escribió:

>
> Thing is, it happens also with an older VM :(
>
> Esteban
>
> > On 15 Jan 2019, at 13:00, Max Leske <[hidden email]> wrote:
> >
> > Actually, I think it's rather a VM problem...?
> >
> >
> > On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:
> >
> >> Hello,
> >>
> >> I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
> >> After doing
> >>
> >> Stdio stdout << ‘OK’
> >>
> >> I’m having this stack:
> >>
> >> File class(ProtoObject)>>primitiveFailed:
> >> File class(ProtoObject)>>primitiveFailed
> >> File class>>fileDescriptorType:
> >> File class>>fileDescriptorIsAvailable:
> >> Stdio class>>standardIOStreamNamed:forWrite:
> >> Stdio class>>stdout
> >> UndefinedObject>>DoIt
> >> OpalCompiler>>evaluate
> >> RubSmalltalkEditor>>evaluate:andDo:
> >> RubSmalltalkEditor>>highlightEvaluateAndDo:
> >> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
> >> MorphicAlarm(MessageSend)>>value
> >> MorphicAlarm>>value:
> >> WorldState>>triggerAlarmsBefore:
> >> WorldState>>runLocalStepMethodsIn:
> >> WorldState>>runStepMethodsIn:
> >> WorldMorph>>runStepMethods
> >> WorldState>>doOneCycleNowFor:
> >> WorldState>>doOneCycleFor:
> >> WorldMorph>>doOneCycle
> >> WorldMorph class>>doOneCycle
> >> [ [ WorldMorph doOneCycle.
> >> Processor yield.
> >> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....
> >> [ self value.
> >> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....
> >>
> >> Con someone confirm or refute this?
> >>
> >> Thanks!
> >> Esteban
> >
>
>

Reply | Threaded
Open this post in threaded view
|

Re: A problem with latest image (64bit) ? (Please confirm)

EstebanLM
Ok, it has to be me :)

Esteban

> On 15 Jan 2019, at 16:36, Martin Dias <[hidden email]> wrote:
>
> Hi,
> I iouldn't reproduce in macos mojave. I downloaded with:
>
> curl https://get.pharo.org/64/70+vmLatest | bash
>
> And no problem with
>
> Stdio stdout << ‘OK’
>
> Report:
>
> ---
> Pharo7.0.0rc1
> Build information:
> Pharo-7.0.0+rc1.build.122.sha.51ac9cae0485c8cbcf23a1bc54c2291a5890c885
> (64 Bit)
> Unnamed
>
> CoInterpreter VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> VM: 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> Date: Sat Jan 5 20:00:11 2019 CommitHash: 7a3c6b6 Plugins:
> 201901051900 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
>
> Mac OS X built on Jan  5 2019 19:11:02 UTC Compiler: 4.2.1 Compatible
> Apple LLVM 7.3.0 (clang-703.0.31)
> VMMaker versionString VM: 201901051900
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Sat Jan 5
> 20:00:11 2019 CommitHash: 7a3c6b6 Plugins: 201901051900
> https://github.com/OpenSmalltalk/opensmalltalk-vm.git
> CoInterpreter VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> StackToRegisterMappingCogit VMMaker.oscog-eem.2504 uuid:
> a00b0fad-c04c-47a6-8a11-5dbff110ac11 Jan  5 2019
> ---
>
> Martín
>
>
> El mar., 15 de ene. de 2019 a la(s) 09:06, Esteban Lorenzano
> ([hidden email]) escribió:
>>
>> Thing is, it happens also with an older VM :(
>>
>> Esteban
>>
>>> On 15 Jan 2019, at 13:00, Max Leske <[hidden email]> wrote:
>>>
>>> Actually, I think it's rather a VM problem...?
>>>
>>>
>>> On 15 Jan 2019, at 12:30, Esteban Lorenzano wrote:
>>>
>>>> Hello,
>>>>
>>>> I’m experiencing a problem with latest image (and latest vm) in Mac (Mojave).
>>>> After doing
>>>>
>>>> Stdio stdout << ‘OK’
>>>>
>>>> I’m having this stack:
>>>>
>>>> File class(ProtoObject)>>primitiveFailed:
>>>> File class(ProtoObject)>>primitiveFailed
>>>> File class>>fileDescriptorType:
>>>> File class>>fileDescriptorIsAvailable:
>>>> Stdio class>>standardIOStreamNamed:forWrite:
>>>> Stdio class>>stdout
>>>> UndefinedObject>>DoIt
>>>> OpalCompiler>>evaluate
>>>> RubSmalltalkEditor>>evaluate:andDo:
>>>> RubSmalltalkEditor>>highlightEvaluateAndDo:
>>>> GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>popupPrint
>>>> MorphicAlarm(MessageSend)>>value
>>>> MorphicAlarm>>value:
>>>> WorldState>>triggerAlarmsBefore:
>>>> WorldState>>runLocalStepMethodsIn:
>>>> WorldState>>runStepMethodsIn:
>>>> WorldMorph>>runStepMethods
>>>> WorldState>>doOneCycleNowFor:
>>>> WorldState>>doOneCycleFor:
>>>> WorldMorph>>doOneCycle
>>>> WorldMorph class>>doOneCycle
>>>> [ [ WorldMorph doOneCycle.
>>>> Processor yield.
>>>> false ] whileFalse: [  ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....
>>>> [ self value.
>>>> Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....
>>>>
>>>> Con someone confirm or refute this?
>>>>
>>>> Thanks!
>>>> Esteban
>>>
>>
>>
>