Debugging-using-the-NDK-CLI-tools: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
=Remote debugging on BlackBerry devices=
#REDIRECT [[Remote_debugging_on_Blackberry_devices]]
 
This page is a how-to on how to setup remote debugging for BlackBerry devices with the command-line tools. Currently the instructions are for Linux and Mac, but should be similar on Windows.
 
Please do not miss the [http://www.gnu.org/software/gdb/documentation/ the <span class="caps">GDB</span> manual] ''[gnu.org]'' to learn how to use <span class="caps">GDB</span>, the command-line debugger.
 
Note that Qt Creator supports remote debugging for BlackBerry devices as well, see this [[Qt-Creator-with-BlackBerry-10|article]] for details. Qt Creator uses the same steps as outlined below, just wraps it into its <span class="caps">IDE</span>.
 
==Pre-requisites==
 
* Allow <span class="caps">SSH</span> connections to your BlackBerry device. See the [[BlackBerry Hints n Tips|BlackBerry Hints and Tips]] article for more details about this.
* Compile your app in the debug mode
 
==Deploying the application==
 
The deployment process is the same as for just testing the application the device:
 
For PlayBook, see the steps described [[Building and Deploying Qt Applications to the Playbook|here]] ''[qt.io]''
 
==Launching the application==
 
As next, you should launch the app on the device and stop it for debugging. <code>blackberry-deploy<code> will do this for you:</code></code>
 
This will stop the execution early on (immediately after the process has been spawned) and wait for the debugger to attach and tell it to continue.
 
The <span class="caps">PID</span> is in the output from blackberry-deploy listed as result::&lt;pid&gt;. You will need this &lt;pid&gt; below to attach to the process.
 
==Attach and setup the debugger==
 
Execute
 
In the <span class="caps">GDB</span> shell, run
 
With the last command from the above block, the app should stop in in the first call in main().
 
Note: <code>$HOST_QTDIR<code> is a path on the development host machine pointing to the root folder of the Qt build for the <span class="caps">ARM</span> target, and '''not''' on the device. <code>$BBNDK<code> refers to the folder where the BlackBerry <span class="caps">NDK</span> is installed. It can contain multiple versions of target and host files. This is why you have to replace &lt;version&gt; with a value which is valid for your environment.</code></code></code></code>
 
==Reading symbols from shared libraries might be unreliable…==
 
If versions of the target libs on the host do not match those on the target, gdb might fail to load symbols from shared libraries. You can check the status of loaded shared libraries by
 
You can enforce reloading of the shared libraries by:
 
<span class="caps">TBD</span>: add information how to download a runtime matching the device libraries.
 
==References==
 
* See the [http://www.qnx.com/developers/docs/6.5.0/index.jsp?topic=/com.qnx.doc.neutrino_prog/using_gdb.html Using <span class="caps">GDB</span>] ''[qnx.com]'' article in the <span class="caps">QNX</span> documentation
 
===Categories:===
 
* [[:Category:BlackBerry|BlackBerry]]

Latest revision as of 07:10, 27 February 2015

Redirect to:

Retrieved from "https://wiki.qt.io/index.php?title=Debugging-using-the-NDK-CLI-tools&oldid=8399"