05-24-2013 10:45 AM
I'm currently setup with a Cascades app over wifi to my Dev AlphaB (10.1.0.1483). I've noticed that as the project grows, the time to hit the "startup" breakpoint while debugging has gone from a few seconds to well over a minute. My project hasn't grown dramatically in size (<10 c++ utility classes, 10 qml assets). My arm executable is sitting at just under 2MB for the debug build. Once started, the debugging and performance seem fine.
Is their anything I can do to speed up debugging time?
05-29-2013 03:56 PM
Look at your Run/Debug configurations and click on the Upload tab. Make sure the option to "Only upload files that have changed and delete old files" is checked. This is much quicker than deploying the entire bar file.
05-30-2013 08:04 AM
The configurations are set as such, and I don't think it's upload related. The application has started (splash screen is shown), it just hangs seemingly forever while the debugger is attaching and getting to the first breakpoint
05-30-2013 09:16 AM
Have you tried connecting over USB instead? That should reduce the time for debug initialization a lot.
If you need to use WiFi the other option would be to try a Run As for most testing and just use Debug As when you need to track down a problem.
05-30-2013 10:57 AM
It reduces it slightly, but we are talking 5+ minutes to 3+ minutes. This is still a massive time for an application to debug especially under rapid code development. For QML editing, it doesn't do any variable checking or highlighting so a simple mistyped variable name can take 10+ minutes to fix even before the functionality can be verified.