README.Android: document how to get pretty-printers work

Change-Id: I0e421aaa38934f6fb2dd8992261ebcde80896e12

README.Android

@@ -25,23 +25,19 @@ In order to have proper acceleration, you need the 32-bit libGL.so:
 	ant debug install
 	adb logcat
 
-	And if all goes well - you should have some nice unit test output to
-enjoy. After a while of this loop you might find that you have lost a lot of
-space on your emulator's or device's /data volume. If using the emulator, you
-can do:
+	And if all goes well - you should have some nice debug output to enjoy
+when you start the app. After a while of this loop you might find that you have
+lost a lot of space on your emulator's or device's /data volume. If using the
+emulator, you can do:
 
 	adb shell stop; adb shell start
 
 but on a (non-rooted) device you probably just need to reboot it. On the other
 hand, this phenomenon might not happen on actual devices.
 
-	and continue onwards & upwards.
-
 * What about using a real device?
 
-	That works fine, too. You won't be able to use the "adb shell
-stop" and "adb shell start" commands to do anything, as far as I
-know. But don't seem to be necessary on a real device anyway?
+	That works fine, too.
 
 * Debugging
 
@@ -50,6 +46,10 @@ know. But don't seem to be necessary on a real device anyway?
 like --enable-selective-debuginfo="sw/" or so, in order to fit into the memory
 during linking.
 
+	Building with all symbols is also possible but the linking is currently
+slow (around 10 to 15 minutes) and you need lots of memory (around 16GB + some
+swap).
+
 	You also want to avoid --with-android-package-name (or when you use
 that, you must set it to "org.libreoffice"), otherwise ndk-gdb will complain
 that
@@ -62,12 +62,12 @@ ERROR: Could not extract package's data directory. Are you sure that
 	cd android/experimental/LOAndroid3
 	<android-ndk-r10d>/ndk-gdb --adb=<android-sdk-linux>/platform-tools/adb --start
 
-	It seems that the "have to start the app before gdb can connect to it"
-and the "pending breakpoints do not work" problems are now resolved with the
-current NDK.
+	Pretty printers aren't loaded automatically due to the single shared
+	object, but you can still load them manually. E.g. to have a pretty-printer for
+	rtl::OString, you need:
 
-Building with all symbols is also possible but the linking is slow (around 10
-to 15 minutes) and you need lots of memory (around 16GB + some swap).
+	(gdb) python sys.path.insert(0, "/master/solenv/gdb")
+	(gdb) source /master/instdir/program/libuno_sal.so.3-gdb.py
 
 * Common Errors / Gotchas