> On 11 Apr 2015, at 21:07, Ben Coman <[email protected]> wrote: > > Returning to build 40486 which exhibits the freeze, as a first step, why > don't we replace all that complicated stack manipulation stuff with... > > NautilusUI>>debugTest: aMethod > [ aMethod methodClass debug: aMethod selector ] fork.
I don’t see any immediate losses. Even the stack should look fine I guess (top context is the one we want etc.). > > cheers -ben > > On Sun, Apr 12, 2015 at 1:31 AM, Clément Bera <[email protected] > <mailto:[email protected]>> wrote: > > > 2015-04-11 1:10 GMT-07:00 Nicolai Hess <[email protected] > <mailto:[email protected]>>: > > > 2015-04-10 17:28 GMT+02:00 Clément Bera <[email protected] > <mailto:[email protected]>>: > 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. > > 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 <[email protected] > <mailto:[email protected]>>: > > 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 <[email protected] >> <mailto:[email protected]>> wrote: >> >> 2015-04-10 2:37 GMT+02:00 Clément Bera <[email protected] >> <mailto:[email protected]>>: >> 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 <[email protected] >> <mailto:[email protected]>>: >> >> >> 2015-04-09 23:38 GMT+02:00 [email protected] <mailto:[email protected]> >> <[email protected] <mailto:[email protected]>>: >> No Debug Tests? >> >> Geez, I am using that all the time. >> >> And you're never encountered this issue 14689 >> <https://pharo.fogbugz.com/default.asp?14689>? >> Or did this work in older versions? >> >> >> >> >> Phil >> >> >> On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <[email protected] >> <mailto:[email protected]>> wrote: >> >> > On 09 Apr 2015, at 22:32, Sean P. DeNigris <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > Nicolai Hess wrote >> >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-tp4805795.html >> >> >> >> <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 >> >> >> >> > > > > >
