Lua Glider IDE breakpoint stop working after stopping/restarting game

This is the version of LuaGlider IDE that I am using:
Product Version: LuaGliderv19 201302132200

I’m using: Corona SDK on Windows
Corona build number: 2013.1137

The problem I’ve run into is that when I set break points when I open up my game project they only seem to work once. Then if I hit the stop button to end the game from running and then try to rerun the game in debug the breakpoints don’t work anymore. I then have to completely restart the debugger (i.e. close off the entire thing and then reopen it) in order for break points to work again. Not sure what the issue is here 

Has anyone else run into this issue?

Thanks,

Hello Avazquez,

We answered your other post. Is this a new issue or is it related to the other post?

Regards,

M.Y. Developers

This is a different issue

Hello Avazquez,

We have never encountered this particular issue before. Please upload the logs via help->upload logs so we can get a better idea of what is going on. 

Regards,

M.Y. Developers

Hello,

As you requested I uploaded the log file after I experienced the issue I mentioned above.

Another issue I noticed is that I have to explicitly go to the drop down menu in order to start the game in debug mode

(i.e. Debug -> Debug Project ) and have the break points work correctly. So if I click the Debug Project button on the UI it will start up the game but won’t hit any break points I set.

FYI, I am running the IDE in trial version mode so not sure if that would also affect functionality

Thanks,

Albert

Hello Albert,

Thank you for the logs. Unfortunately the did not seem to have anything revealing in there. There is no difference between the trial and the full version except the time limit. We are about to do some code cleanup/maintenance and we will keep this issue in mind. The difficult part is we cannot replicate this issue on our machines. The Debug button and the Debug Project button should be debugging the exact same project.

One thing you could try is to set the main project via run-> set main project. If you have multiple projects open it may be trying to debug the wrong one. 

Regards,

M.Y. Developers

No problem. I definitely checked to see that I didn’t have multiple projects opened. After using the IDE for a bit longer I noticed that instead of breakpoints working the first time and then not working the second time that in fact it’s actually an inconsistent thing. In other words sometimes the debug breakpoints work on the 3rd attempt, 4th attempt, 6 attempt, etc… Sometimes I notice it’s a little slow to load up a project and slow to close a project so maybe that delay causes a conflict somehow

Guess I’ll just deal with it for now and hope that the issues are eventually fixed in later releases; it’s at least better than not working with any Corona/LUA IDE. If I discover better repro steps I’ll definitely send them your way

Hello Albert,

One more question. Have you tried restarting the simulator via ctrl-r? Do the breakpoints ever stop working when you try that approach (as opposed to starting a brand new debugger session from the IDE)?

Regards,

M.Y. Developers

Seems to have the same issue, i.e. sometimes the breakpoints don’t work and sometimes they do. I guess this is  at least better than having to completely close off and re open the IDE

Hello Avazquez,

We answered your other post. Is this a new issue or is it related to the other post?

Regards,

M.Y. Developers

This is a different issue

Hello Avazquez,

We have never encountered this particular issue before. Please upload the logs via help->upload logs so we can get a better idea of what is going on. 

Regards,

M.Y. Developers

Hello,

As you requested I uploaded the log file after I experienced the issue I mentioned above.

Another issue I noticed is that I have to explicitly go to the drop down menu in order to start the game in debug mode

(i.e. Debug -> Debug Project ) and have the break points work correctly. So if I click the Debug Project button on the UI it will start up the game but won’t hit any break points I set.

FYI, I am running the IDE in trial version mode so not sure if that would also affect functionality

Thanks,

Albert

Hello Albert,

Thank you for the logs. Unfortunately the did not seem to have anything revealing in there. There is no difference between the trial and the full version except the time limit. We are about to do some code cleanup/maintenance and we will keep this issue in mind. The difficult part is we cannot replicate this issue on our machines. The Debug button and the Debug Project button should be debugging the exact same project.

One thing you could try is to set the main project via run-> set main project. If you have multiple projects open it may be trying to debug the wrong one. 

Regards,

M.Y. Developers

No problem. I definitely checked to see that I didn’t have multiple projects opened. After using the IDE for a bit longer I noticed that instead of breakpoints working the first time and then not working the second time that in fact it’s actually an inconsistent thing. In other words sometimes the debug breakpoints work on the 3rd attempt, 4th attempt, 6 attempt, etc… Sometimes I notice it’s a little slow to load up a project and slow to close a project so maybe that delay causes a conflict somehow

Guess I’ll just deal with it for now and hope that the issues are eventually fixed in later releases; it’s at least better than not working with any Corona/LUA IDE. If I discover better repro steps I’ll definitely send them your way

Hello Albert,

One more question. Have you tried restarting the simulator via ctrl-r? Do the breakpoints ever stop working when you try that approach (as opposed to starting a brand new debugger session from the IDE)?

Regards,

M.Y. Developers

Seems to have the same issue, i.e. sometimes the breakpoints don’t work and sometimes they do. I guess this is  at least better than having to completely close off and re open the IDE