| /external/valgrind/main/coregrind/ |
| pub_core_gdbserver.h | 40 // the previous gdbserver and then activate a new gdbserver
47 // If it returns True, then extern void VG_(gdbserver) can be called
64 Note that gdbserver assumes that software breakpoint is supported
74 /* Entry point invoked by vgdb when it uses ptrace to cause a gdbserver
88 instrumentation for gdbserver.
90 * checks if gdbserver instrumentation is needed for vge.
91 * if no gdbserver instrumentation needed,
94 It will instrument sb_in to allow gdbserver to properly
97 if these are not yet instrumented for gdbserver
[all...] |
| /external/valgrind/main/gdbserver_tests/ |
| README_DEVELOPERS | 3 The Valgrind gdbserver automatic tests are by default
13 or (to just run the gdbserver tests with another gdb):
41 gdbserver tests might often fail due to (irrelevant) differences.
47 the gdbserver tests the following way:
59 If a gdbserver test fails for other reasons, you can run the test
67 using a gdb connected to the gdbserver part of gdb.
72 (e.g. the Valgrind gdbserver understands the 'P' packet,
73 which might not be understood by the gdbserver of gdb).
78 The gdbserver tests are done with various Valgrind tools. A gdbserver
[all...] |
| invoker | 3 # invoker is used to test the invocation of gdbserver.
|
| mcsigpass.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| nlpasssigalrm.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| filter_vgdb | 12 # gdb 7.2 sometimes tries to access address 0x0 (same as with standard gdbserver)
|
| mcclean_after_fork.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| mcinfcallRU.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| filter_memcheck_monitor | 16 # gdb 7.2 sometimes tries to access address 0x0 (same as with standard gdbserver)
|
| mcbreak.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| mcinfcallWSRU.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| mcsignopass.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| mchelp.stdoutB.exp | 42 v.info gdbserver_status : show gdbserver status
48 An additional flag 0b100000000 allows to show gdbserver instrumentation
|
| /external/valgrind/main/coregrind/m_gdbserver/ |
| m_gdbserver.c | 64 init_reason, // initialises gdbserver resources
65 vgdb_reason, // gdbserver invocation by vgdb doing ptrace
66 core_reason, // gdbserver invocation by core (e.g. error encountered)
85 /* An instruction instrumented for gdbserver looks like this:
156 /* Each time gdbserver is called, gdbserver_called is incremented
157 gdbserver_exited is incremented when gdbserver is asked to exit */
177 because they have been (or must be) instrumented for gdbserver.
180 exit of a block that has been instrumented for gdbserver while
182 When gdbserver is not single stepping anymore, all GS_jump entries
374 /* call gdbserver if access kind reported by the too
685 void VG_(gdbserver) ( ThreadId tid ) function
[all...] |
| server.h | 50 /*------------- interface m_gdbserver <=> low level gdbserver */
52 /* Initializes gdbserver. After a call to gdbserver_init, vgdb
53 can contact the gdbserver embedded in valgrind.
54 The rest of the low level gdbserver interface can only
60 /* To be called to indicate that gdbserver usage is finished.
81 /* output some status of gdbserver communication */
92 /* If Valgrind sink was changed by gdbserver:
93 Resets the valgrind sink to before the changes done by gdbserver,
110 /* True if gdbserver is single stepping the valgrind process */
144 /*------------ end of interface to low level gdbserver */
[all...] |
| target.c | 110 void *gdbserver,
116 VG_(dmemcpy) (gdbserver, valgrind, sz, mod);
118 VG_(dmemcpy) (valgrind, gdbserver, sz, mod);
|
| /external/valgrind/main/include/ |
| pub_tool_gdbserver.h | 51 // Calling VG_(gdbserver) with tid > 0 means to let a debugger attach
52 // to the valgrind process. gdbserver will report to gdb that the
54 // tid == 0 indicates to stop gdbserver and report to gdb
57 extern void VG_(gdbserver) ( ThreadId tid );
61 processing in order to enable/disable the call to VG_(gdbserver) in
64 (temporarily) avoid calling gdbserver for error reporting during
69 /* defines the various kinds of breakpoints that gdbserver
71 the gdbserver protocol definition. The level of support
78 instrumentation to be done for gdbserver. This instrumentation
87 just call gdbserver. See memcheck for an example of reusin
[all...] |
| /external/valgrind/main/docs/xml/ |
| manual-core-adv.xml | 17 <listitem><para>Debugging your program using Valgrind's gdbserver
280 <sect1 id="manual-core-adv.gdbserver"
281 xreflabel="Debugging your program using Valgrind's gdbserver and GDB">
282 <title>Debugging your program using Valgrind gdbserver and GDB</title>
290 Valgrind gdbserver to provide a fully debuggable program under
296 <sect2 id="manual-core-adv.gdbserver-simple"
297 xreflabel="gdbserver simple example">
328 Valgrind gdbserver. The sections below describe more advanced
336 <sect2 id="manual-core-adv.gdbserver-concept"
337 xreflabel="gdbserver">
[all...] |
| /ndk/sources/android/libthread_db/gdb-6.6/ |
| libthread_db.c | 33 * cached by gdbserver from the host at init time.
115 * gdbserver to attach to all threads in a target process when
119 * Due to the way gdbserver is coded, this makes gdbserver exit()
122 * be properly rerouted to gdbserver, preventing breakpoints from
127 * are no threads to attach to (gdbserver will attach to the main thread
149 D("Could not get gdbserver permitted caps!\n");
280 * This is nasty, ps_pglobal_lookup is implemented in gdbserver and looks up
|
| /ndk/sources/android/libthread_db/gdb-7.1.x/ |
| libthread_db.c | 29 * cached by gdbserver from the host at init time.
112 * gdbserver to attach to all threads in a target process when
116 * Due to the way gdbserver is coded, this makes gdbserver exit()
119 * be properly rerouted to gdbserver, preventing breakpoints from
124 * are no threads to attach to (gdbserver will attach to the main thread
146 D("Could not get gdbserver permitted caps!\n");
307 * This is nasty, ps_pglobal_lookup is implemented in gdbserver and looks up
|
| /sdk/eclipse/plugins/com.android.ide.eclipse.ndk/src/com/android/ide/eclipse/ndk/internal/launch/ |
| NdkGdbLaunchDelegate.java | 216 // kill existing gdbserver
220 if (description != null && description.contains("gdbserver")) { //$NON-NLS-1$
248 // launch gdbserver
251 GdbServerTask gdbServer = new GdbServerTask(device, manifestData.getPackage(),
253 new Thread(gdbServer,
254 String.format("gdbserver for %s", manifestData.getPackage())).start(); //$NON-NLS-1$
256 // wait for gdbserver to attach
267 // if gdbserver failed to attach, we report any errors that may have occurred
269 if (gdbServer.getLaunchException() != null) {
272 gdbServer.getLaunchException())
[all...] |
| /ndk/ |
| ndk-gdb | 67 # Delay in seconds between launching the activity and attaching gdbserver on it.
268 echo " --delay=<secs> Delay in seconds between activity start and gdbserver attach."
271 echo " --port=<port> Use tcp:localhost:<port> to communicate with gdbserver [$DEBUG_PORT]"
373 # $1: Package name ("com.example.hellojni") or program name ("/lib/gdbserver")
526 # If gdbserver exists, then we built with 'ndk-build NDK_DEBUG=1' and it's
529 if [ -f $PROJECT/libs/$COMPAT_ABI/gdbserver ] ; then
530 log "Found gdbserver under libs/$COMPAT_ABI, assuming app was built with NDK_DEBUG=1"
545 if [ ! -f $PROJECT/libs/$COMPAT_ABI/gdbserver ] ; then
546 echo "ERROR: Could not find gdbserver binary under $PROJECT/libs/$COMPAT_ABI"
555 # Let's check that 'gdbserver' is properly installed on the device too. If thi
[all...] |
| /ndk/build/tools/ |
| build-target-prebuilts.sh | 74 # First, gdbserver
78 dump "Building $GDB_TOOLCHAIN gdbserver binaries..."
79 run $BUILDTOOLS/build-gdbserver.sh "$SRC_DIR" "$NDK_DIR" "$GDB_TOOLCHAIN" $FLAGS
|
| /ndk/build/core/ |
| setup-toolchain.mk | 95 # We expect the gdbserver binary for this toolchain to be located at its root.
96 TARGET_GDBSERVER := $(TOOLCHAIN_ROOT)/prebuilt/gdbserver
103 # Ensure that for debuggable applications, gdbserver will be copied to
106 NDK_APP_GDBSERVER := $(NDK_APP_DST_DIR)/gdbserver
119 @ $(HOST_ECHO) "Gdbserver : [$(PRIVATE_NAME)] $(call pretty-dir,$(PRIVATE_DST))"
|
| /frameworks/compile/libbcc/gdb_plugin/ |
| android-commands.py | 18 # GDB plugin to allow debugging of apps on remote Android systems using gdbserver.
84 return os.path.join(self.data_directory, "lib", "gdbserver")
350 # Update gdbserver status
436 # Port for gdbserver
479 'prebuilt', 'android-arm', 'gdbserver', 'gdbserver')
482 # Install gdbserver
486 print "Unable to push gdbserver to device. Try re-installing app."
496 print "--==Remote gdbserver Started " \
500 # Forward port for gdbserver
[all...] |
