Complete
over 4 years ago

If issue is still present, please resubmit a bug report.

Debugger challenges - not able to set breakpoints

Hi,

Very frustrated over the last couple of weeks with the debugger being absolutely useless. Every time I set a breakpoint and start the code executing it tells me I can't set a breakpoint. This is a widget/glance.

I normally use prints but have hit a problem where the app storage fails to read in the simulator. I found two things: firstly the simulator was picking up another apps dataset due to some name overlap and secondly when I reset and deleted data in the app the initialisation code now fails to setup any storage according to the simulator.

The code itself has worked in other apps and also worked until I changed a class to a module as a revised version had no need for a class.

I've tried re-installing the SDK and eclipse plug-in separately and together. I've also tried previous versions of the SDK. Same crash on read of store and no debugging capability.

Almost had enough of these tools. Note the debugging doesn't work in visual studio either.

Any ideas welcome besides reverting the code (this doesn't help the debugger but might fix crash).

Regards,

David  

  • Hi Jim. 

    Thanks for the quick feedback. I had previously deleted the current widget's data and reset the app which had no effect. I also tried deleting all apps. I think the store clash previously was due to me not changing the UUID but I did do this after seeing this error.

    The store still has no values and the debugger can't set breakpoints. However, the debugger can set breakpoints and trigger them in another app. So something about the code structure/use of glance is confusing it.

    I'll try two experiments:

    1. Remove glance function and make it a widget only

    2. Revert my storage handling back to a class (code would execute but not debug previously)

    any other ideas welcome.

    Regards,

    David

  • Have you tried File>Delete All Apps in the sim?  This kind of sounds like you have multiple prg files with the same manifest ID.