From 6acd5f949bb69f5bb69e50f97f8570dab26fb8b6 Mon Sep 17 00:00:00 2001 From: Julian Seward Date: Thu, 27 Oct 2011 10:57:00 +0000 Subject: [PATCH] Merge from trunk, r12239 (Some small doc updating for 3.7.0.) git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_7_BRANCH@12244 --- docs/xml/manual-core-adv.xml | 37 +++++++++++++++++++++++++++++++++++- docs/xml/manual-core.xml | 4 ++-- docs/xml/vg-entities.xml | 6 +++--- 3 files changed, 41 insertions(+), 6 deletions(-) diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index 2039f6f10c..717c2f2e5e 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -512,7 +512,7 @@ gdb prog ]]> GDB will use a local tcp/ip connection to connect to the Android adb forwarder. Adb will establish a relay connection between the host system and the Android -target system. Pay attention to use the GDB delivered in the +target system. Be sure to use the GDB delivered in the Android NDK system (typically, arm-linux-androideabi-gdb), as the host GDB is probably not able to debug Android arm applications. Note that the local port nr (used by GDB) must not necessarily be equal @@ -520,6 +520,41 @@ to the port number used by vgdb: adb can forward tcp/ip between different port numbers. +In the 3.7.0 release, the GDB server is not enabled by default +for Android, due to problems in establishing a suitable directory in +which Valgrind can create the necessary FIFOs (named pipes) for +communication purposes. You can stil try to use the GDB server, but +you will need to explicitly enable it using the flag +--vgdb=yes or +--vgdb=full. + + +Additionally, you +will need to select a temporary directory which is (a) writable +by Valgrind, and (b) supports FIFOs. This is the main difficult +point. Often, /sdcard satisfies +requirement (a), but fails for (b) because it is a VFAT file system +and VFAT does not support pipes. Possibilities you could try are +/data/local, +/data/local/Inst (if you +installed Valgrind there), or +/data/data/name.of.my.app, if you +are running a specific application and it has its own directory of +that form. This last possibility may have the highest probability +of success. + +You can specify the temporary directory to use either via +the --with-tmpdir= configure time +flag, or by setting environment variable TMPDIR when running Valgrind +(on the device, not the Android device). + + +We hope to have a better story for temporary directory handling +on Android in the future. The difficulty is that, unlike in standard +Unixes, there is no single temporary file directory that reliably +works across all devices and scenarios. + + On ARM, essentially the entire ARMv7-A instruction set is supported, in both ARM and Thumb mode. ThumbEE and Jazelle are - not supported. NEON and VFPv3 support is fairly complete. ARMv6 - media instruction support is mostly done but not yet complete. + not supported. NEON, VFPv3 and ARMv6 media support is fairly + complete. diff --git a/docs/xml/vg-entities.xml b/docs/xml/vg-entities.xml index 52c1d0ec9f..1b5adb1a15 100644 --- a/docs/xml/vg-entities.xml +++ b/docs/xml/vg-entities.xml @@ -2,12 +2,12 @@ - + - - + + -- 2.47.2