On 7 February 2012 19:48, Eliot Miranda <
eliot.miranda@gmail.com> wrote:
>
>
>
> On Tue, Feb 7, 2012 at 7:36 AM, Igor Stasenko <
siguctua@gmail.com> wrote:
>>
>>
>> On 7 February 2012 17:16, Andreas Raab <
andreas.raab@gmx.de> wrote:
>> >
>> >
>> >
>> > On 2/7/2012 16:06, Igor Stasenko wrote:
>> >>
>> >>
>> >> On 7 February 2012 08:48, Andreas Raab<
andreas.raab@gmx.de> wrote:
>> >>>
>> >>> On 2/7/2012 3:39, Igor Stasenko wrote:
>> >>>>
>> >>>> however, in pharo we already introduced the threadId ivar:
>> >>>>
>> >>>> Link subclass: #Process
>> >>>> instanceVariableNames: 'suspendedContext priority myList threadId
>> >>>> errorHandler name env'
>> >>>> classVariableNames: ''
>> >>>> poolDictionaries: ''
>> >>>> category: 'Kernel-Processes'
>> >>>>
>> >>>> could it be because of initial "warning, processHasThreadId flag is
>> >>>> unset; cannot function as a threaded VM if so."?
>> >>>
>> >>>
>> >>> Yes. The VM doesn't actually look at class Process - it only checks the
>> >>> flag
>> >>> in the image header.
>> >>
>> >> So it is probably needs to be fixed to have warning which not lying to you
>> >> :)
>> >
>> >
>> > The warning is entirely correct, it tells you that the processHasThreadId
>> > ->FLAG<- isn't set.
>> >
>> warning: Process doesn't have threadId; VM will not thread
>>
>> wheere you see any mention about flag?
>> i think that it is clear to everyone who reading the above that it is
>> not about flag, but
>> about mising thread id var in Process.
>
>
> Whatever. The VM doesn't know how to interrogate the class Process to find if it has the inst var. You tell the VM that Process has the inst var by setting the flag and saving the image. You set the flag using bit 0 of VM parameter 48. Find a nice accessor attached.