Re: [Pharo-users] Debugger with inlined methods

2016-10-13 Thread Clément Bera
Well for quick methods it's doable. For inlined control flow operations it's quite difficult. Although it could be possible now with the mustBeBoolean magic thingy... On Thu, Oct 13, 2016 at 3:23 PM, Vitor Medina Cruz wrote: > Ben, > > I was thinking the same as you, I

Re: [Pharo-users] Debugger with inlined methods

2016-10-13 Thread Vitor Medina Cruz
Ben, I was thinking the same as you, I think that if I could set the image in development mode, or something like that, it would not do such optimization so that debugger behaves more like expected. If the debugger could undo such optimizations would be fine also. I just assumed it should be hard

Re: [Pharo-users] Debugger with inlined methods

2016-10-12 Thread Clément Bera
The simulation of primitives is done in Context>>#doPrimitive:method:receiver:args: Basically, specific numbers are simulated in the image while other numbers are run using the VM code. Quick methods (what you call inlined methods) are encoded with primitive numbers between 256 and 512. If you

Re: [Pharo-users] Debugger with inlined methods

2016-10-12 Thread Ben Coman
On Tue, Oct 11, 2016 at 9:45 PM, Esteban Lorenzano wrote: > >> On 11 Oct 2016, at 15:43, Vitor Medina Cruz wrote: >> >> Hello, >> >> I was TTDing today with Pharo and some odd thing happened. I had a method >> that just returned false and while

[Pharo-users] Debugger with inlined methods

2016-10-11 Thread Vitor Medina Cruz
Hello, I was TTDing today with Pharo and some odd thing happened. I had a method that just returned false and while debugging I could not step into it (i wanted to change the method while debugging), I suppose the method was inlined and so debugging was not available, is that correct? Regards,