Hi,
I was suffering from this infinite loop since a long time. Last week I
thought I was able to reproduce it but as soon as I tried to fix it I
could not reproduce it anymore... So I wasn't able to tell if I fixed it
or not.
The only thing I can say is that this is difficult to interrupt not
because of the logging (which is a problem for large stacks) but because
this is caused by a short lived process that spawns new processes. Thus,
lots of processes are created and the interruptions could interrupt any
of them...
Hillaire, if you have an image with the problem, can you forward it to
me? I'm looking forward to kill this bug with my axe.
Guille
-------- Original Message --------
Hi denis
Could you propose a way to speed up the stack? Write less :)
Because interrupting an endless or other would be good.
Stef
Le 18/9/16 à 16:52, Denis Kudriashov a écrit :
2016-09-18 15:26 GMT+02:00 Hilaire <hila...@drgeo.eu
<mailto:hila...@drgeo.eu>>:
I guess you meant SpecDebugger.
I can alt+., but at the end I have to kill Pharo from the system.
Enclosed the .log file.
I don't know why there is lot of noise in the debug log, it is
hard to
understand what is going on.
Hilaire. In lastest Pharo we investigate why process interruption
with cmd+. is not working sometime.
Main reason was that system write stack to file before opening
debugger. And it could be really slow which will delay debugger for
the long time.
That's why I suggest disable logging. In my cases it makes cmd+.
works well.
