does anyone knows?
Esteban |
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-tp4805795.html Debugger enters infinite loop when closed after editing test with "doesNotUnderstand: #stepToCallee" errors MNU: receiver of "stepToCallee" is nil |
In reply to this post by EstebanLM
What is that?
Le 9/4/15 20:05, Esteban Lorenzano a écrit : > does anyone knows? > > Esteban > > |
Administrator
|
In reply to this post by Nicolai Hess
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?
Cheers,
Sean |
> On 09 Apr 2015, at 22:32, Sean P. DeNigris <[hidden email]> 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 |
No Debug Tests?
Geez, I am using that all the time. Phil On Thu, Apr 9, 2015 at 10:21 PM, Marcus Denker <[hidden email]> wrote:
|
2015-04-09 23:38 GMT+02:00 [hidden email] <[hidden email]>:
And you're never encountered this issue 14689? Or did this work in older versions?
|
I was using it frequently too and I have never experienced any issues... 2015-04-09 14:58 GMT-07:00 Nicolai Hess <[hidden email]>:
|
me too, and also never seen it. but also never seen the issue… so I suppose is my fault not to talk in time :) I will propose a replacement as soon as I can allocate some time to came up with something more or less well designed (bah… or designed “my way” which is not always “well” :P). Esteban
|
In reply to this post by Clément Béra
2015-04-10 2:37 GMT+02:00 Clément Bera <[hidden email]>:
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.
|
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
|
Well I guess I used to click proceed and not close the debugger... 2015-04-10 1:24 GMT-07:00 Max Leske <[hidden email]>:
|
2015-04-10 17:28 GMT+02:00 Clément Bera <[hidden email]>:
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 would love that. I know a couple of people who already complained about the test debug feature missing and I think that said feature is really an important point of the IDE. That being said, it will probably mean delaying the release another week or two. Then again, releasing something in a good state is better IMHO than releasing on time. Cheers, Max
|
In reply to this post by Nicolai Hess
I miss it. I think I remember that a <Restart> <Close> would work, so a hack fix could be the do a restart when the close button is pushed. Reintroducing it with the problem fixed would be welcome. cheers -ben On Sat, Apr 11, 2015 at 4:10 PM, Nicolai Hess <[hidden email]> wrote:
|
In reply to this post by Max Leske
+1 On Sat, Apr 11, 2015 at 3:58 PM, Max Leske <[hidden email]> wrote:
|
In reply to this post by Nicolai Hess
2015-04-11 1:10 GMT-07:00 Nicolai Hess <[hidden email]>:
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.
|
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. cheers -ben On Sun, Apr 12, 2015 at 1:31 AM, Clément Bera <[hidden email]> wrote:
|
On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <[hidden email]> wrote:
Sorry. Pretend I didn't say that. That is the <run test> behaviour. cheers -ben |
In reply to this post by Ben Coman
I don’t see any immediate losses. Even the stack should look fine I guess (top context is the one we want etc.).
|
Free forum by Nabble | Edit this page |