Lines Matching full:device
18 already-running <code>globaltime</code> application, execute the following, making sure that: 1) you do this from the same window used to build the software on the device you are debugging and 2) verify that the symbols in the object files in the build tree match up with what is installed on the device or emulator.</p>
25 <p>Android runs <code>gdbserver</code> on the device and an ARM aware <code>gdb</code>, named <code>arm-eabi-gdb</code>, on the desktop machine.</p>
28 run <code>gdbserver</code> on the device:<BR>
33 The <code>:5039</code> tells gdbserver to listen on port 5039 on the localhost, which adb bridges from the host to the device. <code>executable</code> represents the command to debug, a common one being runtime -s which starts the entire system all running in a single process. <br>
44 <p>At this point <code>gdb</code> will connect with your device
46 able to enter <code>c</code> to have the device start executing inside of the
52 <li>On the device, launch a new command:
57 <li>On your workstation, forward port 5039 to the device with adb:
68 Where <i>product-name</i> is the name of the device product that you're building (for example, <code>sooner</code>),
80 <i>absolute-source-path</i> is the path to your source tree; for example, <code>/work/device</code> or <code>/Users/hoser/android/device</code>.<BR>
84 <li>Connect to the device by issuing the <code>gdb</code> command:<BR>
90 The <code>:5039</code> tells <code>gdb</code> to connect to the localhost port 5039, which is bridged to the device by <code>adb</code>.<BR>
99 the <code>gdb</code> remote protocol doesn't have a way for the device to
103 device when a
108 system process, most likely your device will be frozen at this point. <strong>Do not press the home key</strong>. Bring the device to someone who can
110 If you're in the field and just want your device to continue as it
141 % cd <top of device source tree>
