Troubles with IDE - simulator locks up, can't debug (on Mac - fine on Windows)

Solar2D General Questions/Discussion
#1

Hey folks,

I am new to Lua, and to Corona, and iOS, and to Mac OS… So I am learning an awful lot lately :slight_smile:

I have a basic puzzle game that I’ve been working on in just textWrangler and the emulator, but things got a bit more complicated and I’ve needed to move to Sublime Text 2 + Corona Editor to try to debug a little better. I made the switch while I was traveling on business on my Windows laptop and everything worked pretty well.

But when I got back home I loaded up the latest revision of my code on my Mac and there are some problems. The code runs just fine in the emulator, but if I run it from Sublime Text (F10 or the Corona Editor menu) it locks up about 10 seconds after launching, every single time. Spinning beach ball. Again, it runs totally fine when it’s *not* run from the Sublime IDE which was confusing to me. Didn’t get this error on Windows.

Also variable view in the Corona Editor in Sublime tells me “Local Variable display disabled with this version of Corona SDK (2511). Try a build after 2515.” But 2511 is the newest one? I didn’t get this error on Windows either. So basically I can’t view variables when debugging.

One last issue that happens on both Mac and PC - for some inexplicable reason, every time I run from Sublime, execution halts on a ‘require’ line from my main.lua as if there were a breakpoint there, but there isn’t a breakpoint. On Mac the emulator gives an error “Unexpected Response from Simulator 202 Paused <path to file> <line # of require statement>” and a notification to check console for errors… and there are none. It proceeds fine if I hit F10, but it’s a nuisance.

Sorry for all the questions, and thanks in advance.

#2

Seeing the exact same thing. Any word on when this will be addressed?

#3

This should be addressed with the latest daily build.

Rob

#4

Rob, is there a resolution for this?  I am experiencing the same issue.  “Unexpected response from Simulator: 202 Paused …” on the first line of code (a require statement).  OS-X.  Happens with Corona build 2014.2511.  I tried latest daily build, 2015.2617, and get the same error.  Happens in Sublime Text 3, (Stable Channel, Build 3083), as well as in the older Sublime Text 2.  I tried a package control update on Corona plugin as well as a full uninstall, then reinstall of Corona plugin.  The error persists.  Thanks.
 

#5

What happens if you just use Corona Simulator and keep Sublime Text out of it?

Rob

#6

Rob, Projects will run with Corona Simulator and also run fine when just “Run” from within the editor. 

The error occurs when attempting to run the Corona debugger from within the Corona Editor (in Sublime Text).  The error occurs on the first line of code regardless of the code (same as reported by the user “euphemismism” above).

I hope this helps.

#7

Rob, One more data point: running the debugger from within Lua Glider also works without error.  The reported error appears to be specific to the Corona Editor plugin for Sublime Text.  Thanks.

#8

Sorry to hear you’re having trouble with Corona Editor.  Can you PM me the Sublime Text console output (for the entire session) when this happens?  Type Ctrl+` to open the Sublime Text console.  Also, open Corona Editor > About Corona Editor… before copying the console and that will put version info in the console.  At this stage, I would definitely recommend using Sublime Text 3 rather than 2.

Note that there is always a virtual breakpoint on the first line of code in your app so I think that explains the behavior you are seeing with it stopping on the require statement.  If you put a print() statement before the require() does that change anything?  Is the require() loading one of your files or a third party library?  Does this problem occur with the Sample Apps?  If so, which one?

#9

Seeing the exact same thing. Any word on when this will be addressed?

#10

This should be addressed with the latest daily build.

Rob

#11

Hello all,

even when I’m not expert on this, I can notify that this problem occurs only the first time you run a project. The second time works just fine. Next one fails, next one works.

Is quite annoying to be honest.

I’ve tried as well with Sublime Text 3 and occurs the same behavior.

Hope this can be fixed. Anyway, running the project directly on the simulator works fine. So my recomendation is just to have the simulator with the project open and then setup it to run on any change. With that, just save your project and it will run directly.

The problem with that is that you cannot use the debug function… 

Best regards,

/JGG

#12

Just tried Sublime 3 with Corona Editor, and it is still unusable. It would be nice to be able to debug!

#13

You should be able to debug with Corona Editor.  It supports setting break points, stepping in and out of functions, watching variable, etc.

How is it not working?

Rob

#14

mimetic,

I also had a problem running Corona debugger in Sublime 3 (reported above).  Perry Clarke discovered that I had a space in my project path which caused the debugger to hang.  Eliminating the space in the directory name solved the problem.

Pete

#15 
Unexpected response from Simulator: 202 Paused /Volumes/Macintosh HD/Users/dgross/Corona Projects/photobook/main.lua 10 Check Console for error messages.

Well, it starts with this…which might be just the initial break. So, I tell it to continue (run), but it is so slow I can’t tell what’s happening.

Before, it was freezing (Sublime was freezing), so I gave up.

It is taking 2 minutes to run what takes .3 seconds in simulator.

So…I don’t feel I can count on it.

#16

Rob, is there a resolution for this?  I am experiencing the same issue.  “Unexpected response from Simulator: 202 Paused …” on the first line of code (a require statement).  OS-X.  Happens with Corona build 2014.2511.  I tried latest daily build, 2015.2617, and get the same error.  Happens in Sublime Text 3, (Stable Channel, Build 3083), as well as in the older Sublime Text 2.  I tried a package control update on Corona plugin as well as a full uninstall, then reinstall of Corona plugin.  The error persists.  Thanks.
 

#17

What happens if you just use Corona Simulator and keep Sublime Text out of it?

Rob

#18

There used to be an issue with spaces in pathnames but I thought that was fixed a while back.

Which version of Corona Editor are you running?   Corona Editor > About Corona Editor…

Also, which version of CoronaSDK?

#19

I saw the reference to pathnames, but I didn’t see how it applied. That is, in the whole path? Or somewhere in some config file? Too vague to help.

Latest CoronaSDK, both Sublime 2 & 3, etc.

Just too unstable to use.

If I knew how else to report to you, I would. Please advise.

#20

The issue was with spaces in the project path as the original poster noted.

There are two spaces in your path:

/Volumes/Macintosh HD/Users/dgross/Corona Projects/photobook/main.lua

You can help by giving me the version info I asked for :slight_smile:

Which version of Corona Editor are you running?  Issue this command in Sublime Text  Corona Editor > About Corona Editor… , either screenshot the dialog that results or copy the same info from the Sublime Text console (Ctrl+`) and post it here.

 

Also, specifically which version of CoronaSDK?  The “latest” Public Release, the “latest” Daily Build?  I’m looking for a version number.