Re: [Pharo-dev] Puzzled

2014-04-05 Thread Eliot Miranda
Hi Stef, I think it is because forContext:priority: does not schedule the process, just creates it. The debugger code steps the process but after stepping the process is still not runnable. So the process terminate is unnecessary; the process should not have been added to the run queue and

Re: [Pharo-dev] Puzzled

2014-04-05 Thread Eliot Miranda
On Sat, Apr 5, 2014 at 10:30 AM, Eliot Miranda eliot.mira...@gmail.comwrote: Hi Stef, I think it is because forContext:priority: does not schedule the process, just creates it. The debugger code steps the process but after stepping the process is still not runnable. So the process

Re: [Pharo-dev] Puzzled

2014-04-05 Thread Pharo4Stef
In fact there was an error in the debugger code = endless loop in another thread it was strange because the test was not returning On 05 Apr 2014, at 19:30, Eliot Miranda eliot.mira...@gmail.com wrote: Hi Stef, I think it is because forContext:priority: does not schedule the process,

Re: [Pharo-dev] Puzzled

2014-04-04 Thread Sven Van Caekenberghe
It is hard for everyone to get a complex issue cleanly integrated. On 04 Apr 2014, at 08:30, Pharo4Stef pharo4s...@free.fr wrote: I’m sorry but I will stop working on this issue since I do not have time for pharo anymore this week and the next one. Apparently I’m the only one to care about

Re: [Pharo-dev] Puzzled

2014-04-04 Thread Pharo4Stef
Thanks camille apparently I restarted from a clean image but may be I merged. Could you try loading the latest version of 12460 and let me know? On 04 Apr 2014, at 09:21, Camille Teruel camille.ter...@gmail.com wrote: I tried on my machine in latest image and no matter how many times I run this

Re: [Pharo-dev] Puzzled

2014-04-04 Thread Camille Teruel
Fix in inbox https://pharo.fogbugz.com/f/cases/13170/ On 4 avr. 2014, at 12:46, Camille Teruel camille.ter...@gmail.com wrote: On 4 avr. 2014, at 12:37, Pharo4Stef pharo4s...@free.fr wrote: Thanks camille apparently I restarted from a clean image but may be I merged. Could you try

[Pharo-dev] Puzzled

2014-04-03 Thread Pharo4Stef
Hi guys I need your brain cells. When I execute the test testBasic | context process debugger printedString | context := [ 20 factorial ] asContext. process := Process forContext: context priority: Processor userInterruptPriority.

Re: [Pharo-dev] Puzzled

2014-04-03 Thread Pharo4Stef
even using ensure: to make sure that the process is terminated it is not really working. I have the impression that there is a problem and that the tests does not really finishes but this is really difficult to debug. Hi guys I need your brain cells. When I execute the test

Re: [Pharo-dev] Puzzled

2014-04-03 Thread Pharo4Stef
When I use | context process | context := [ 20 factorial ] asContext. process := Process forContext: context priority: Processor userInterruptPriority. [ debugger := Smalltalk tools debugger new process:

Re: [Pharo-dev] Puzzled

2014-04-03 Thread Pharo4Stef
| context process debugger | context := [ 20 factorial ] asContext. process := Process forContext: context priority: Processor userInterruptPriority. [ debugger := Smalltalk tools debugger new process:

Re: [Pharo-dev] Puzzled

2014-04-03 Thread Pharo4Stef
ok now I understand: an endless loop inside the debugger creation. I do not understand why we did not address it with clement because we open the debugger and other when we fixed the logic of the inspector (to avoid polling refresh). Stef On 03 Apr 2014, at 21:13, Pharo4Stef pharo4s...@free.fr

Re: [Pharo-dev] Puzzled

2014-04-03 Thread Clément Bera
Hey, I remembered removing the initializeAutoRefresh code from the debugger. Perhaps I didn't commit that package. Or I forgot this one. 2014-04-03 12:34 GMT-07:00 Pharo4Stef pharo4s...@free.fr: ok now I understand: an endless loop inside the debugger creation. I do not understand why we did