Le 11 avr. 2015 14:32, "Clément Bera" <bera.clem...@gmail.com> a écrit : > > > > 2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaih...@web.de>: > >> >> >> 2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clem...@gmail.com>: >>> >>> Well I guess I used to click proceed and not close the debugger... >> >> >> >> I don't know who is working on the breakpoint support and I don't know how long it will take. >> Maybe we can fix thie image freeze and re-include the debugtest code until the new breakpoint support. >> >> what do you think? >> > > I think break points were done by Clara Allende. As far as I know, they work but there's no IDE support for them. I think they are not ready for this release but I am not sure about the status. Marcus can confirm it will not be ready.
For this release the intention was reviewing and integrating the Reflectivity machinery, and then afterwards the breakpoints. So far Marcus has done a lot on that part (reviewing and enhancing my prototype for reflectivity), and we have discussed that the breakpoints (in the state I've left them at the end of my internship) should work out of the box. Nevertheless, I want to do a pass on them and update what's necessary once Pharo4 is released. But they won't be integrated in the release, that's for sure, because there's work to do with them... Cheers Clari > > Yes this image freeze could be fixed but I can't really work on the Pharo release this week (I'm working with Eliot on Cogit...). I could review the fix if you want just tagged me in fogbugz. >>> >>> >>> 2015-04-10 1:24 GMT-07:00 Max Leske <maxle...@gmail.com>: >>> >>>> For a little more context: the issue was originally raised by Clara in the thread titled "MNU: receiver of "stepToCallee:" is nil”. IIRC the issue was easily reproducible when debugging a test, then closing the debugger (via the close icon). Clicking “Proceed” on the other hand gracefully terminated the process. >>>> >>>> Cheers, >>>> Max >>>> >>>> >>>>> On 10 Apr 2015, at 09:56, Nicolai Hess <nicolaih...@web.de> wrote: >>>>> >>>>> 2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clem...@gmail.com>: >>>>>> >>>>>> I was using it frequently too and I have never experienced any issues... >>>>> >>>>> >>>>> Ok, can you describe a use case, what test case you can start and >>>>> close the debugger without image freeze? >>>>> >>>>> Maybe we can find what is the difference between that >>>>> test case and those that freeze the image, and than find a fix. >>>>> >>>>>> >>>>>> >>>>>> 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaih...@web.de>: >>>>>> >>>>>>> >>>>>>> 2015-04-09 23:38 GMT+02:00 p...@highoctane.be <p...@highoctane.be>: >>>>>>>> >>>>>>>> No Debug Tests? >>>>>>>> >>>>>>>> Geez, I am using that all the time. >>>>>>> >>>>>>> >>>>>>> And you're never encountered this issue 14689? >>>>>>> Or did this work in older versions? >>>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Phil >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker < marcus.den...@inria.fr> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> > On 09 Apr 2015, at 22:32, Sean P. DeNigris < s...@clipperadams.com> wrote: >>>>>>>>> > >>>>>>>>> > Nicolai Hess wrote >>>>>>>>> >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-tp4805795.html >>>>>>>>> > >>>>>>>>> > Ah, I miss that too! From that thread, it seems it was removed temporarily >>>>>>>>> > until we have real breakpoints. Is there an issue for its return? >>>>>>>>> > >>>>>>>>> >>>>>>>>> Not yet. >>>>>>>>> >>>>>>>>> Marcus >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
