why we removed debugTest from nautilus?
2015-04-09 20:05 GMT+02:00 Esteban Lorenzano <estebanlm@gmail.com>:
does anyone knows?
Esteban
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... 14689 <https://pharo.fogbugz.com/default.asp?14689> Debugger enters infinite loop when closed after editing test with "doesNotUnderstand: #stepToCallee" errors 14060 <https://pharo.fogbugz.com/default.asp?14060> MNU: receiver of "stepToCallee" is nil
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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 -- View this message in context: http://forum.world.st/why-we-removed-debugTest-from-nautilus-tp4818657p48186... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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 <marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 <marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
I was using it frequently too and I have never experienced any issues... 2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 <marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
On 10 Apr 2015, at 02:37, Clément Bera <bera.clement@gmail.com> wrote:
I was using it frequently too and I have never experienced any issues⦠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
2015-04-09 14:58 GMT-07:00 Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>>: 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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...>
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
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 <marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>>: 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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...>
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
Well I guess I used to click proceed and not close the debugger... 2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 <marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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?
2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 <marcus.denker@inria.fr
wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
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 <nicolaihess@web.de> wrote:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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?
2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 < marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
Hi nicolai I do not know the complexity of the fix and its addition. I have the impression that we will have more fixes after the release than in 3.0. So prepare it because it can always be used either in 4.0 or 5.0 alpha. Even if at the end we remove it because of better wy to express breakpoint. In france we say "never free the prey for its shadow" ;) Stef Le 11/4/15 14:58, Ben Coman a écrit :
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 <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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?
2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@gmail.com <mailto:maxleske@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>>:
No Debug Tests?
Geez, I am using that all the time.
And you're never encountered this issue14689 <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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
> On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote: > > Nicolai Hess wrote >> http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... > > 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
On 11 Apr 2015, at 10:10, Nicolai Hess <nicolaihess@web.de> wrote:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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 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
2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@gmail.com <mailto:maxleske@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>>: 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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...>
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
+1 On Sat, Apr 11, 2015 at 3:58 PM, Max Leske <maxleske@gmail.com> wrote:
On 11 Apr 2015, at 10:10, Nicolai Hess <nicolaihess@web.de> wrote:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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 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
2015-04-10 1:24 GMT-07:00 Max Leske <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 < marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess@web.de>:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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. 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 <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 < marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
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 <bera.clement@gmail.com> wrote:
2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess@web.de>:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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.
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 <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@highoctane.be>:
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 < marcus.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc@openinworld.com> 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.
Sorry. Pretend I didn't say that. That is the <run test> behaviour. cheers -ben
On 11 Apr 2015, at 21:31, Ben Coman <btc@openinworld.com> wrote:
On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc@openinworld.com <mailto:btc@openinworld.com>> 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.
Sorry. Pretend I didn't say that. That is the <run test> behaviour.
Really? Why does it send #debug: then??
cheers -ben
>From the perspective of a TestCase... * "running" a test wraps execution in error handling so it can log errors without TestRunner breaking open a debugger. * "debugging" executes without that error handling so an error breaks open a debugger. The functionality required is that a debugger opens immediately on the first line of the test method. cheers -ben On Sun, Apr 12, 2015 at 3:35 AM, Max Leske <maxleske@gmail.com> wrote: > > On 11 Apr 2015, at 21:31, Ben Coman <btc@openinworld.com> wrote: > > > > On Sun, Apr 12, 2015 at 3:07 AM, Ben Coman <btc@openinworld.com> 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. >> >> > Sorry. Pretend I didn't say that. That is the <run test> behaviour. > > > Really? Why does it send #debug: then?? > > cheers -ben > > >
On 11 Apr 2015, at 21:07, Ben Coman <btc@openinworld.com> 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 <bera.clement@gmail.com <mailto:bera.clement@gmail.com>> wrote:
2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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.
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 <maxleske@gmail.com <mailto:maxleske@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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 <nicolaihess@web.de <mailto:nicolaihess@web.de>>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <mailto:phil@highoctane.be> <phil@highoctane.be <mailto:phil@highoctane.be>>: 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 <marcus.denker@inria.fr <mailto:marcus.denker@inria.fr>> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <sean@clipperadams.com <mailto:sean@clipperadams.com>> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t... <http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...>
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
Le 11 avr. 2015 14:32, "Clément Bera" <bera.clement@gmail.com> a écrit :
2015-04-11 1:10 GMT-07:00 Nicolai Hess <nicolaihess@web.de>:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@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 <maxleske@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 <nicolaihess@web.de> wrote:
2015-04-10 2:37 GMT+02:00 Clément Bera <bera.clement@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 <nicolaihess@web.de>:
2015-04-09 23:38 GMT+02:00 phil@highoctane.be <phil@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.denker@inria.fr> wrote:
On 09 Apr 2015, at 22:32, Sean P. DeNigris <
sean@clipperadams.com> wrote:
Nicolai Hess wrote
http://forum.world.st/do-we-need-to-debug-testmethods-from-within-Nautilus-t...
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
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...
The problem is that it needs compiler changes that will not be done for Pharo4. Maybe we can back port, but the priority for me is not Pharo4 for this. Marcus
Hi, i'm really missing the debug feature in nautilus. +1 to restore it! But it's worse than what others describe, lets say you write a tests that fails, i've to press ALT + "." to've the UI back and the dialog window that offers you to proceed, abandon, debug, etc. It hangs on this collaboration of PackageTreeNautilusUI#runTestForAMethod:notifying:priority: testSemaphoreForMethod wait. I also tried to send #haltOnce or #halt into the test and it doesn't work on a test. It stops only when i press ALT + "." Cheers, Francisco On Sun, Apr 12, 2015 at 7:00 AM, Marcus Denker <marcus.denker@inria.fr> wrote:
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...
The problem is that it needs compiler changes that will not be done for Pharo4. Maybe we can back port, but the priority for me is not Pharo4 for this.
Marcus
Load the Slice #16018 into your Pharo 4 image and it will add the menu item back. Francisco Ortiz Peñaloza wrote
Hi,
i'm really missing the debug feature in nautilus. +1 to restore it!
But it's worse than what others describe, lets say you write a tests that fails, i've to press ALT + "." to've the UI back and the dialog window that offers you to proceed, abandon, debug, etc.
It hangs on this collaboration of PackageTreeNautilusUI#runTestForAMethod:notifying:priority:
testSemaphoreForMethod wait.
I also tried to send #haltOnce or #halt into the test and it doesn't work on a test. It stops only when i press ALT + "."
Cheers, Francisco
On Sun, Apr 12, 2015 at 7:00 AM, Marcus Denker <
marcus.denker@
> wrote:
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...
The problem is that it needs compiler changes that will not be done for Pharo4. Maybe we can back port, but the priority for me is not Pharo4 for this.
Marcus
-- View this message in context: http://forum.world.st/why-we-removed-debugTest-from-nautilus-tp4818657p48389... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 11 Apr 2015, at 10:10, Nicolai Hess <nicolaihess@web.de> wrote:
2015-04-10 17:28 GMT+02:00 Clément Bera <bera.clement@gmail.com <mailto:bera.clement@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?
Breakpoints are for Pharo5⦠maybe back porting will be possible, but it is not the priority. Marcus
participants (13)
-
Ben Coman -
Clara Allende -
Clément Bera -
Esteban Lorenzano -
Francisco Ortiz Peñaloza -
kilon alios -
Marcus Denker -
Max Leske -
Nicolai Hess -
Paul DeBruicker -
phil＠highoctane.be -
Sean P. DeNigris -
stepharo