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

diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml
index 2039f6f10c5acb957806c92f74a059ccd2dae25a..717c2f2e5ee3811b13b46ecf57b8e42c628602fb 100644 (file)
--- a/docs/xml/manual-core-adv.xml
+++ b/docs/xml/manual-core-adv.xml
@@ -512,7 +512,7 @@ gdb prog
 ]]></screen>
 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.
 </para>
 
+<para>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 
+<computeroutput>--vgdb=yes</computeroutput> or
+<computeroutput>--vgdb=full</computeroutput>.
+</para>
+
+<para>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, <computeroutput>/sdcard</computeroutput> 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
+<computeroutput>/data/local</computeroutput>,
+<computeroutput>/data/local/Inst</computeroutput> (if you
+installed Valgrind there), or
+<computeroutput>/data/data/name.of.my.app</computeroutput>, 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.</para>
+
+<para>You can specify the temporary directory to use either via
+the <computeroutput>--with-tmpdir=</computeroutput> configure time
+flag, or by setting environment variable TMPDIR when running Valgrind
+(on the device, not the Android device).
+</para>
+
+<para>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.
+</para>
+
 </sect2>
 
 <sect2 id="manual-core-adv.gdbserver-commandhandling"

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index b1c98cba3bce3660508b6bc9887e207dad08a7a4..736c39756f03d2deeacd42338ea2d45c4a6d4298 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -2021,8 +2021,8 @@ subject to the following constraints:</para>
   <listitem>
    <para>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.
    </para>
   </listitem>
 

diff --git a/docs/xml/vg-entities.xml b/docs/xml/vg-entities.xml
index 52c1d0ec9f30248df1c888056d68129e0b856f3d..1b5adb1a15c244b8fc0bd4288183dbbec1115d85 100644 (file)
--- a/docs/xml/vg-entities.xml
+++ b/docs/xml/vg-entities.xml
@@ -2,12 +2,12 @@
 <!ENTITY vg-jemail     "julian@valgrind.org">
 <!ENTITY vg-vemail     "valgrind@valgrind.org">
 <!ENTITY cl-email      "Josef.Weidendorfer@gmx.de">
-<!ENTITY vg-lifespan   "2000-2010">
+<!ENTITY vg-lifespan   "2000-2011">
 
 <!-- valgrind release + version stuff -->
 <!ENTITY rel-type    "Release">
-<!ENTITY rel-version "3.6.0">
-<!ENTITY rel-date    "21 October 2010">
+<!ENTITY rel-version "3.7.0">
+<!ENTITY rel-date    "2 November 2011">
 
 <!-- where the docs are installed -->
 <!ENTITY vg-docs-path  "$INSTALL/share/doc/valgrind/html/index.html">