Searched refs:gdbserver (Results 1 – 25 of 58) sorted by relevance
123
| /external/valgrind/main/coregrind/m_gdbserver/ |
| D | README_DEVELOPERS | 2 to gdbserver in valgrind.
4 How to use Valgrind gdbserver ?
9 What is gdbserver ?
24 gdb stub in small boards, or gdbserver when the remote computer runs
32 The standard gdb distribution has a standalone gdbserver (a small
37 Activation of gdbserver code inside valgrind
39 The gdbserver code (from gdb 6.6, GPL2+) has been modified so as to
41 debugged by a gdb speaking to this gdbserver embedded in valgrind.
42 The ptrace system calls inside gdbserver have been replaced by reading
45 The gdbserver functionality is activated with valgrind command line
[all …]
|
| /external/valgrind/main/docs/internals/ |
| D | arm_thumb_notes_gdbserver.txt | 2 about gdbserver, read coregrind/m_gdbserver/README_DEVELOPERS
3 about gdbserver tests, read gdbserver_tests/README_DEVELOPERS).
5 ARM thumb and gdbserver
15 at several places in the gdbserver code.
24 => the breakpoints are stored in the gdbserver breakpoints hash table
30 When instrumenting a SB for gdbserver, a PUT of the current instruction
31 address is done to the IP, to ensure that the gdbserver helper call
37 As gdbserver instrumentation code uses the IstMark to find the IP
45 instruction must be discarded to have the SB re-instrumented for gdbserver.
52 Due to this "off by one", gdbserver is discarding a range of two bytes
[all …]
|
| /external/valgrind/main/gdbserver_tests/ |
| D | 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
84 Typically, a gdbserver test implies to launch two programs:
[all …]
|
| D | nlsigvgdb.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
8 # The control-c will cause a character to be sent to gdbserver, causing
9 # an invocation while the gdbserver is already busy.
|
| D | nlsigvgdb.vgtest | 1 # Tests the case when gdb sends a character to gdbserver while
2 # the gdbserver was forced invoked just before.
3 # gdbserver must send a signal to itself that is wait-ed for by vgdb.
|
| D | nlpasssigalrm.vgtest | 1 # test that signals that must be "directly" passed by gdbserver
4 # by telling gdbserver (with QPassSignals packet) to pass
|
| D | mcmain_pic.vgtest | 1 # test that gdbserver/gdb properly handle a PIC executable
3 # information via the gdbserver protocol packet qXfer:auxv:read:
|
| D | nlgone_return.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | nlfork_chain.vgtest | 1 # test that gdbserver properly cleans up its resources in a chain
|
| D | nlgone_abrt.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | mcmain_pic.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | nlgone_exit.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | mssnapshot.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | nlself_invalidate.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | mcsigpass.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | nlself_invalidate.vgtest | 1 # reproduces a bug triggered by translation chaining and gdbserver
|
| D | mcwatchpoints.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| D | hginfo.stdinB.gdb | 1 # connect gdb to Valgrind gdbserver:
|
| /external/skia/platform_tools/android/bin/ |
| D | android_gdbserver | 56 adb_push_if_needed $ANDROID_TOOLCHAIN/../gdbserver data/local/tmp
63 $ADB shell ps | grep gdbserver | awk '{print $2}' | xargs $ADB shell kill
68 $ADB shell /data/local/tmp/gdbserver :5039 /data/local/tmp/skia_launcher ${APP_ARGS[@]} &
|
| D | android_gdb_apk | 19 $ADB shell ps | grep gdbserver | awk '{print $2}' | xargs -r $ADB shell kill
31 adb_push_if_needed $ANDROID_TOOLCHAIN/../gdbserver /data/local/tmp
41 $ADB shell /data/local/tmp/gdbserver :$PORT --attach $PID &
|
| /external/chromium_org/third_party/skia/platform_tools/android/bin/ |
| D | android_gdb_apk | 19 $ADB shell ps | grep gdbserver | awk '{print $2}' | xargs -r $ADB shell kill
31 adb_push_if_needed $ANDROID_TOOLCHAIN/../gdbserver /data/local/tmp
41 $ADB shell /data/local/tmp/gdbserver :$PORT --attach $PID &
|
| D | android_gdbserver | 71 adb_push_if_needed $ANDROID_TOOLCHAIN/../gdbserver /data/local/tmp
78 $ADB shell ps | grep gdbserver | awk '{print $2}' | xargs $ADB shell kill
83 $ADB shell LD_LIBRARY_PATH=/data/local/tmp:\$LD_LIBRARY_PATH /data/local/tmp/gdbserver :5039 /data/…
|
| /external/chromium_org/build/android/ |
| D | adb_gdb | 126 --gdbserver=*)
269 Otherwise, the script will complain, but you can use the --gdbserver,
530 BINARY=$NDK_DIR/prebuilt/android-$ARCH/gdbserver/gdbserver
532 BINARY=$(get_ndk_toolchain_prebuilt "$NDK_DIR" "$ARCH" gdbserver)
620 GDBSERVER_PIDFILE="$TMPDIR"/gdbserver-$TMP_ID.pid
739 TARGET_GDBSERVER=/data/local/tmp/gdbserver-adb-gdb-$TMP_ID
948 GDBSERVER_LOG=$TMPDIR/gdbserver-$TMP_ID.log
|
| /external/valgrind/main/ |
| D | README.android_emulator | 65 # You have on the android side a gdbserver
67 gdbserver :1234 your_exe
|
| /external/valgrind/main/include/ |
| D | pub_tool_gdbserver.h | 58 extern void VG_(gdbserver) ( ThreadId tid );
|
123