I see its in 60383. Thx Denis.
cheers -ben
On Thu, Feb 9, 2017 at 5:29 PM, Denis Kudriashov wrote:
> I made fix with LocalRecursionStopper. Look at fogbugs.
>
> 2017-02-08 17:13 GMT+01:00 Denis Kudriashov :
>>
>> Problem is related to RecursionStopper
I made fix with LocalRecursionStopper. Look at fogbugs.
2017-02-08 17:13 GMT+01:00 Denis Kudriashov :
> Problem is related to RecursionStopper which not releases "stop method"
> while first debugger will be close or step over.
> Also this "stop method" is Halt>>once which
Indeed. (We should one of these days improve the concurrent aspect of Pharo
but we should finish first the current open work)
On Wed, Feb 8, 2017 at 5:13 PM, Denis Kudriashov
wrote:
> Problem is related to RecursionStopper which not releases "stop method"
> while first
Problem is related to RecursionStopper which not releases "stop method"
while first debugger will be close or step over.
Also this "stop method" is Halt>>once which could be mistake.
Probably RecoursionStopper should be process specific variable and not
global registry.
2017-02-08 17:04
That's strange.
I found that if you step over halt then you are able to halt on next call.
Anyway it needs to be fixed
2017-02-08 16:37 GMT+01:00 Ben Coman :
>
> This has bugged me a few times recently, so I've produced a demo.
> Define...
>
> Object subclass: #AA
>
2017-02-08 16:37 GMT+01:00 Ben Coman :
>
> This has bugged me a few times recently, so I've produced a demo.
> Define...
>
> Object subclass: #AA
> instanceVariableNames: ''
> classVariableNames: ''
> package: ''
>
> AA>>test
> self haltOnce.
> self inform: 'I got
This has bugged me a few times recently, so I've produced a demo.
Define...
Object subclass: #AA
instanceVariableNames: ''
classVariableNames: ''
package: ''
AA>>test
self haltOnce.
self inform: 'I got here'.
then in playground evaluate
Halt resetOnce. "i.e. World > Debugging >