Cleanup the android scripts.

platform_tools/android/bin/android_gdb_native

 #!/bin/bash
 #
-# android_gdb: Pushes gdbserver. Connects and enters debugging environment.
+# android_gdb_native: Pushes gdbserver, connects to specified Skia app,
+#                     and enters command line debugging environment.
 
 SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
 source $SCRIPT_DIR/android_setup.sh
 
 # setup the gdbserver
 export BUILDTYPE  # from android_setup.sh
 $SCRIPT_DIR/android_gdbserver -d ${DEVICE_ID} ${APP_ARGS[@]}
 
 # quit if gdbserver setup failed
 if [[ "$?" != "0" ]]; then
@@ skipping 26 matching lines @@
     # Load libskia_android.so here.
     echo "sharedLibrary skia_android"
 } > $GDBSETUP
 
 
 # Launch gdb client
 echo "Entering gdb client shell"
 GDB_COMMAND=$(command ls "$ANDROID_TOOLCHAIN"/*-gdb | head -n1)
 "$GDB_COMMAND" -x $GDBSETUP
 
-# Clean up
-rm -rf $GDB_TMP_DIR
+# Clean up:
+# We could 'rm -rf $GDB_TMP_DIR', but doing so would cause subsequent debugging
+# sessions to take longer than necessary. The tradeoff is to now force the user
+# to remove the directory when they are done debugging.

[scroggo, 2015/02/09 14:03:32]

Any way for the user to know this? If it ever matters, should we add a
convenient way to do this?

[djsollen, 2015/02/10 13:47:20]

I think it is more convenient to just rm -rf the directory than adding an option
to the debugging script to do it for them.  

+rm $GDBSETUP