Lines Matching refs:to

10 The Android NDK r4 introduced a helper shell script named 'ndk-gdb' to
20 Where $NDK points to your NDK installation path. You can also create an
21 alias or add $NDK to your PATH to avoid typing it every time.
33      element that sets the android:debuggable attribute to "true"
37      ndk-gdb will not work if you try to run your application on
45      If you are using the ADT Eclipse plug-in to build your
77 or --launch=<name> option to automatically start your activity before the
80 When it successfully attaches to your application process, ndk-gdb will give
81 you a normal GDB prompt, after setting up the session to properly look for
96            these libraries corresponding to your target device on your
106   Only needed to debug problems when you can't connect and that the
116 > By default, ndk-gdb will try to attach to an existing running instance
117   of your application on the target device. You can use --start to
121         application manifest. Use `--launch=<name>` to start another one.
122         See `--launch-list` to dump the list of such activities.
125 > This is similar to --start, except that it allows you to start a specific
134 > Specify application project directory. Useful if you want to launch
135   the script without cd-ing to the directory before that.
138 > By default, ndk-gdb will use local TCP port 5039 to communicate with
140   to natively debug programs running on different devices/emulators
141   connected to the same development machine.
147 > These flags are similar to the ADB ones and allow you to handle the
148   case where you have several devices/emulators connected to your
151         -d:          Connect to a single physical device
152         -e:          Connect to a single emulator device
153         -s <serial>: Connect to a specific device or emulator
158   to list a specific device, without the need for a specific option.
162 > After connecting to the debugged process, run the GDB initialization
163   commands found in <file>. This is useful if you want to do something
169   may cause early breakpoints to be missed.
176 > Extra flag(s) to pass to the ndk-build system when querying it for
183   When linking statically to a libstdc++ library, the required printers
190 'ndk-gdb' requires a Unix shell to run. This means that Cygwin is required
191 to run it on Windows. An experimental Python re-implementation called
202 not be able to debug native threads properly. Instead, the debugger will only
203 be able to put breakpoints on the main thread, completely ignoring the
206 The root of the problem is complex, but is essentially due to a very unfortunate
209 The gdbserver binary that comes with this NDK has special code to detect this
211 you don't have anything special to do when building your code).
216   platform bug-fix back-ported to it, you will be able to debug native
219 - If you are not, you will only be able to debug the main thread