Bug in IDE on Mac 4.6.2 dp 1

[marksmithhfx]

HI,

I didn't know where else to post this (so please let me know if there is a better home for bug reports).

this relates to the Ticked-Off app that was developed in the recent Summer Academy (since RR has access to this application I'll use it as the reference).

OSX 10.6.7
LC 4.6.2 dp 1

If I open the resources stack-> images card and set a breakpoint on the card script "resizeImages" (setting it anywhere seems to trigger the problem), close the script window and resize the main stack the script is triggered, the code displayed and at this point the IDE is frozen requiring a forced quit.

-- Mark

[marksmithhfx]

Seems I left one step out: you have to actually step into the code before it hangs. I've also tried by setting a variable watch on a variable in resizeImages and get the same IDE hang.

-- Mark

[shaosean]

support AT runrev DOT com will take your bug reports

[marksmithhfx]

support AT runrev DOT com will take your bug reports

Thanks

[runrevGAf68e]

I have this exact same problem except I'm using 5.0.2.

I'm going to submit as well. Let me know if you have an existing ticket number.

[runrevGAf68e]

FYI : I've opened ticket 2012022610000602 for this issue.

[runrevGAf68e]

FYI : This is a known existing issue. Here is the ticket :

http://quality.runrev.com/show_bug.cgi?id=2867

[mwieder]

It's also bug #9896. The debugger locks up because the resizeStack handler is still in control.

Note that this wouldn't be that hard a problem for runrev to fix if they felt like it. PowerDebug doesn't have this problem.

http://www.ahsoftware.net/PowerTools/Po ... DDemo.html
http://www.ahsoftware.net/PowerTools/BuyPowerDebug.irev
http://PowerDebug.ahsoftware.net

[bn]

Hi,

I ran just the other day into debugging a resizeStack handler and shure enough it crashed the IDE.

My workaround was to take the code out of the resizeStack handler and put it into another handler

Code: Select all

on resizeStack newWidth,newHeight,oldWidth,oldHeight
   
   -- code taken out of resizeStack handler because it it difficult to debug
   -- Debugger can not debug when the operating system is taking over like in resizeStack
   -- by sending it after completion of resizeStack handler (send xxx in 10 milliseconds) Livecode is on its own again and can debug

  send "adjust newWidth,newHeight,oldWidth,oldHeight" to me in 10 milliseconds
   
end resizeStack

on adjust newWidth,newHeight,oldWidth,oldHeight
   lock screen
   ## your code for the resize handler here
   unlock screen
end adjust

now I can debug the code for the resizeStack handler. The way it is now it is not well suited for "live resizing" because the messages stack up (funny to watch though).
But once your code is OK you can put it back into the resizeStack handler.

Or you get PowerDebug, which I also use but had it turned off at the moment.

Kind regards

Bernd

[mwieder]

There are various other handlers that will get you into trouble as well with the IDE's debugger - preOpenStack handlers, for example. Anything where an error can cause a lockup situation because control hasn't returned from the handler in the stack under test.