Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Native Development

Reply
Developer
Posts: 74
Registered: ‎03-04-2012
My Device: developer
My Carrier: developer
Accepted Solution

Debugging QML code

Hi All,

 

Is there any way to attach debugger with java script code written QML file in cascades development for Blackberry 10

 

Regards

 

Deepak Charya
Developer
Posts: 1,524
Registered: ‎12-18-2012
My Device: Z30, Z10 LE, DevAlpha C, PlayBook

Re: Debugging QML code

This page describes how to setup QML debugging but I'm not sure if this works in current SDK:

https://developer.blackberry.com/cascades/documentation/getting_started/tools/debugging.html

 

 


Andrey Fidrya, @zmeyc on twitter
New Developer
Posts: 52
Registered: ‎01-09-2012
My Device: PlayBook
My Carrier: Fido

Re: Debugging QML code

Hi i'm trying to debug my cascades project i'm using the gold sdk

 

when i tell it to debug it throws an error

 

 

Defined

#define

QT_DECLARATIVE_DEBUG   

#include

<Qt/qdeclarativedebug.h>   in the main.cpp and enabled javascript  debugging

 

Error in final launch sequence
Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
Cannot access memory at address 0x1b974f0

 

How do i debug it ???

 

My code ran fine  "Normally " no debuggin untill i included some entra code an now hangs during  load

and need to trace where / why .......

New Developer
Posts: 52
Registered: ‎01-09-2012
My Device: PlayBook
My Carrier: Fido

Re: Debugging QML code

i looked at the workbench log and found this at the end

 

!ENTRY com.qnx.tools.ide.qde.ui 4 5012 2013-05-25 04:39:09.209
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:114)
at com.qnx.tools.ide.qde.internal.ui.launch.dsf.QDEDSFLaunchConfigurationDelegate.launchDebugSession(QDEDSFLaunchConfigurationDelegate.java:186)
at com.qnx.tools.ide.qde.internal.ui.launch.dsf.QDEDSFLaunchConfigurationDelegate.launch(QDEDSFLaunchConfigurationDelegate.java:95)
at com.qnx.tools.ide.bbt.debug.ui.internal.launch.BBTDSFLaunchConfigurationDelegate.launch(BBTDSFLaunchConfigurationDelegate.java:70)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.Exception: Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:889)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:720)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2013-05-25 04:39:09.210
!MESSAGE Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
!STACK 0
java.lang.Exception: Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:889)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:720)

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:39:12.381
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:39:12.521
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:39:14.231
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:39:16.377
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.ide.qde.ui 4 5012 2013-05-25 04:40:48.522
!MESSAGE Error in final launch sequence
!STACK 1
org.eclipse.core.runtime.CoreException: Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.concurrent.Query.get(Query.java:114)
at com.qnx.tools.ide.qde.internal.ui.launch.dsf.QDEDSFLaunchConfigurationDelegate.launchDebugSession(QDEDSFLaunchConfigurationDelegate.java:186)
at com.qnx.tools.ide.qde.internal.ui.launch.dsf.QDEDSFLaunchConfigurationDelegate.launch(QDEDSFLaunchConfigurationDelegate.java:95)
at com.qnx.tools.ide.bbt.debug.ui.internal.launch.BBTDSFLaunchConfigurationDelegate.launch(BBTDSFLaunchConfigurationDelegate.java:70)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.Exception: Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:889)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:720)
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2013-05-25 04:40:48.523
!MESSAGE Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
!STACK 0
java.lang.Exception: Cannot access memory at address 0x1b974f0
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.processMIOutput(AbstractMIControl.java:889)
at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$RxThread.run(AbstractMIControl.java:720)

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:40:52.183
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:40:52.946
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:40:54.661
!MESSAGE Unable to determine the application exit code

!ENTRY com.qnx.tools.bbt.core 4 0 2013-05-25 04:40:58.697
!MESSAGE Unable to determine the application exit code

Developer
Posts: 93
Registered: ‎03-27-2013
My Device: Dev Alpha C,Z10 LE
My Carrier: China Unicom

Re: Debugging QML code

[ Edited ]

I often click the Debug icons and see the device log.The debug icon is at the upper right.

New Developer
Posts: 52
Registered: ‎01-09-2012
My Device: PlayBook
My Carrier: Fido

Re: Debugging QML code

yeah but why doesn't debugging work ?

 

New Developer
Posts: 52
Registered: ‎01-09-2012
My Device: PlayBook
My Carrier: Fido

Re: Debugging QML code

[ Edited ]

Does debugging even work in QML ? i have step filters enabled I can tell it to run and it runs but when i click debug i get an error Error in final launch sequence
Failed to execute MI command:
-exec-continue
Error message from debugger back end:
Cannot access memory at address 0x1b974f0
Cannot access memory at address 0x1b974f0

 I can set breakpoint to no avail cause i CAN'T debug.....so whats the advantage of using the GOLD sdk ?

 

If this is how it works accross the board no wonder apps are taking foreve to be built.