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  

Parents
  • Further update.

    1. Removing glance annotation and making this an app runs fine and debuuger works with breakpoints being triggered.

    2. Debugging on a Venu as a widget it all gets loaded as a glance as expected. Debugger fails to set any breakpoints or removes them when app is run

    3. Debugging as a widget with glance annotation means debugger removes all breakpoints as per (2)

    My conclusion is that there is a bug in the debugger when glance annotation is used

Comment
  • Further update.

    1. Removing glance annotation and making this an app runs fine and debuuger works with breakpoints being triggered.

    2. Debugging on a Venu as a widget it all gets loaded as a glance as expected. Debugger fails to set any breakpoints or removes them when app is run

    3. Debugging as a widget with glance annotation means debugger removes all breakpoints as per (2)

    My conclusion is that there is a bug in the debugger when glance annotation is used

Children
No Data