Le 2020-08-19 15:24, Esteban Maringolo a écrit : > There is a similar view in Pharo 8, the Browse breakpoints show breakpoints > and halts as well.
The P8 view does not allow for dynamic activation, and that logic is only in P9. Steven. > However, I avoid using breakpoints because you cannot add/remove them within > the debugger, and sometimes with nested blocks it is hard to specify which > expression should get it. > > Regards! > > Esteban A. Maringolo > > On Wed, Aug 19, 2020 at 5:27 AM Steven Costiou <steven.cost...@kloum.io> > wrote: > > So, I just checked and we have this view in Pharo 9 with all halts and > breakpoints. > > We just need to put a global checkbox to (de)activate everything at once (and > polish a little bit the view). > > Le 2020-08-19 10:11, Steven Costiou a écrit : > > Hi, > > in Pharo 9/NewTools we added the possibility to disable a halt or a > breakpoint through a checkbox in the inspector or from a view in the debugger. > For example this is an inspector on a test object: > > When a halt is disabled this way, it is still in your code but instead of > halting it logs into the Transcript. > We planned to have a global view somewhere with a global "checkbox" to > enable/disable them all. > But this will be only for Pharo 9. > > But to me it has interest only if you want to keep dormant debugging > capabilities in production, that you awake when you have a problem that you > need to debug. > Otherwise, I would do as Tim suggested and make sure there are no halts in > the production image. > > Steven. > > Le 2020-08-18 22:46, Esteban Maringolo a écrit : > Hi, > > I was bit by a bug in production I couldn't identify and it ended up > being a lost halt in the code that was hanging my whole image. So no > bug at all, a feature :-) > > Is there a way to disable the #halt and breakpoints? > This way I could add such an expression (if existent) to my server > startup and avoid issues like this. > > Regards! > > Esteban A. Maringolo
