Re: [Pharo-dev] stepping off the end of the debug stack

2017-04-08 6:46 GMT+02:00 Ben Coman : > As an immediate stop-gap I'm adding the following comment to > BlockClosure>>newProcess > > "IMPORTANT! Debug stepping this deep infrastructure may lock your Image" > "If you are not sure what you are doing, close the debugger now." >

Re: [Pharo-dev] stepping off the end of the debug stack

Hi Ben, 2017-04-08 6:32 GMT+02:00 Ben Coman : > I imagine a newcomer exploring the system could easily step off the end of > the debug stack like this... > > (1 printString) "debugIt" > then StepOver six times where the image hangs at "Processor > terminateActive" > >

Re: [Pharo-dev] stepping off the end of the debug stack

Hi Ben, hmmm, good thought. Seems to me that the right solution is in the primitive simulations in Context>>tryPrimitive... or Context>>doPrimitive... (*) so that the debugger process isn't terminated, but the process being debugged is. (* at my phone right now so don't have the code to

Re: [Pharo-dev] stepping off the end of the debug stack

2017-04-08 6:46 GMT+02:00 Ben Coman : > > > On Sat, Apr 8, 2017 at 12:32 PM, Ben Coman wrote: > >> >> I imagine a newcomer exploring the system could easily step off the end >> of the debug stack like this... >> >> (1 printString) "debugIt" >> then

Re: [Pharo-dev] stepping off the end of the debug stack

On Sat, Apr 8, 2017 at 12:32 PM, Ben Coman wrote: > > I imagine a newcomer exploring the system could easily step off the end of > the debug stack like this... > > (1 printString) "debugIt" > then StepOver six times where the image hangs at "Processor > terminateActive" >