|
From: <sv...@va...> - 2011-10-27 10:06:04
|
Author: sewardj
Date: 2011-10-27 11:01:17 +0100 (Thu, 27 Oct 2011)
New Revision: 12239
Log:
Some small doc updating for 3.7.0.
Modified:
trunk/docs/xml/manual-core-adv.xml
trunk/docs/xml/manual-core.xml
trunk/docs/xml/vg-entities.xml
Modified: trunk/docs/xml/manual-core-adv.xml
===================================================================
--- trunk/docs/xml/manual-core-adv.xml 2011-10-27 06:22:23 UTC (rev 12238)
+++ trunk/docs/xml/manual-core-adv.xml 2011-10-27 10:01:17 UTC (rev 12239)
@@ -512,7 +512,7 @@
]]></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 @@
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"
Modified: trunk/docs/xml/manual-core.xml
===================================================================
--- trunk/docs/xml/manual-core.xml 2011-10-27 06:22:23 UTC (rev 12238)
+++ trunk/docs/xml/manual-core.xml 2011-10-27 10:01:17 UTC (rev 12239)
@@ -2021,8 +2021,8 @@
<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>
Modified: trunk/docs/xml/vg-entities.xml
===================================================================
--- trunk/docs/xml/vg-entities.xml 2011-10-27 06:22:23 UTC (rev 12238)
+++ trunk/docs/xml/vg-entities.xml 2011-10-27 10:01:17 UTC (rev 12239)
@@ -2,12 +2,12 @@
<!ENTITY vg-jemail "ju...@va...">
<!ENTITY vg-vemail "val...@va...">
<!ENTITY cl-email "Jos...@gm...">
-<!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">
|