[Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Tim Mackinnon
Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup that if I restart a method in the debugger - particularly from a breakpoint or correcting a dnu issue the environment frequently locks up. Fearing the worst (after a few seconds), if I repeatedly press cmd . (Say 5 times) aft

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Tim Mackinnon
I should also mention these extra debuggers don’t have the stack either, just a single dnu method. Tim Ps thank god for close windows to right. ... Sent from my iPhone > On 8 Jun 2018, at 12:30, Tim Mackinnon wrote: > > Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup t

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Norbert Hartl
> Am 08.06.2018 um 13:30 schrieb Tim Mackinnon : > > Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup that > if I restart a method in the debugger - particularly from a breakpoint or > correcting a dnu issue the environment frequently locks up. Fearing the worst > (after

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Esteban A. Maringolo
On 08/06/2018 08:30, Tim Mackinnon wrote: > Hi, I’ve noticed lately when using a reasonably recent Pharo 6.1 setup that > if I restart a method in the debugger - particularly from a breakpoint or > correcting a dnu issue the environment frequently locks up. Fearing the worst > (after a few secon

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Tim Mackinnon
Good point by Norbert - I should have referenced a bug - but interested in others experience and I will annotate that bug. For me, this isn’t a recursion thing, it’s a dnu when restarting a method (not sure if many people do this - but it’s a key Smalltalk feature in my mind - so it should work

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Steven Costiou
Concerning the bug 22085, i commented on fogbuzz: > I believe it is because when running test cases, it runs through: > > runCaseForDebug: aTestCase > [...call test code...] > on: self class failure , self class skip, self class warning, self class error > do: [:ex | ex sunitAnnounce: aTestCase t

Re: [Pharo-users] Pharo 6, bad debugger behaviour

2018-06-08 Thread Tim Mackinnon
Ah that’s interesting- it’s happened to me 4 or 5 tines in the last 2 days. Recent enough that maybe I can figure out a test case I’ll try. Sent from my iPhone > On 8 Jun 2018, at 18:57, Steven Costiou wrote: > > Concerning the bug 22085, i commented on fogbuzz: > >> I believe it is becau