Adding option to use gdbtui instead of gdb to adb_gdb

build/android/adb_gdb

 #!/bin/bash
 #
 # Copyright (c) 2012 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 #
 
 # A generic script used to attach to a running Chromium process and
 # debug it. Most users should not use this directly, but one of the
 # wrapper scripts like adb_gdb_content_shell, or adb_gdb_drt
@@ skipping 63 matching lines @@
 
 # Allow wrapper scripts to set the program name through ADB_GDB_PROGNAME
 PROGNAME=${ADB_GDB_PROGNAME:-$(basename "$0")}
 
 ACTIVITY=$DEFAULT_ACTIVITY
 ADB=
 ANNOTATE=
 # Note: Ignore BUILDTYPE variable, because the Ninja build doesn't use it.
 BUILDTYPE=
 FORCE=
+GDBEXEPOSTFIX=gdb
 GDBINIT=
 GDBSERVER=
 HELP=
 NDK_DIR=
 NO_PULL_LIBS=
 PACKAGE_NAME=
 PID=
 PROGRAM_NAME="activity"
 PULL_LIBS=
 PULL_LIBS_DIR=
@@ skipping 62 matching lines @@
       ;;
     --symbol-dir=*)
       SYMBOL_DIR=$optarg
       ;;
     --target-arch=*)
       TARGET_ARCH=$optarg
       ;;
     --toolchain=*)
       TOOLCHAIN=$optarg
       ;;
+    --ui)
+      GDBEXEPOSTFIX=gdbtui
+      ;;
     --verbose)
       VERBOSE=$(( $VERBOSE + 1 ))
       ;;
     --debug)
       BUILDTYPE=Debug
       ;;
     --release)
       BUILDTYPE=Release
       ;;
     -*)
@@ skipping 104 matching lines @@
   --verbose             Increase verbosity.
 
   --sandboxed           Debug first sandboxed process we find.
   --sandboxed=<num>     Debug specific sandboxed process.
   --symbol-dir=<path>   Specify directory with symbol shared libraries.
   --package-name=<name> Specify package name (alternative to 1st argument).
   --program-name=<name> Specify program name (cosmetic only).
   --pid=<pid>           Specify application process pid.
   --force               Kill any previous debugging session, if any.
   --start               Start package's activity on device.
+  --ui                  Use gdbtui instead of gdb
   --activity=<name>     Activity name for --start [$DEFAULT_ACTIVITY].
   --annotate=<num>      Enable gdb annotation.
   --script=<file>       Specify extra GDB init script.
 
   --gdbserver=<file>    Specify targer gdbserver binary.
   --gdb=<program>       Specify host gdb client binary.
   --target-arch=<name>  Specify NDK target arch.
   --adb=<program>       Specify host ADB binary.
 
   --pull-libs           Force system libraries extraction.
@@ skipping 220 matching lines @@
   if [ -d "$TOOLCHAIN/bin" ]; then
     TOOLCHAIN=$TOOLCHAIN/bin
   fi
   ANDROID_TOOLCHAIN=$TOOLCHAIN
 fi
 
 # Cosmetic: Remove trailing directory separator.
 ANDROID_TOOLCHAIN=${ANDROID_TOOLCHAIN%/}
 
 # Find host GDB client binary
-GDB=$(which $ANDROID_TOOLCHAIN/*-gdb 2>/dev/null | head -1)
+GDB=$(which $ANDROID_TOOLCHAIN/*-$GDBEXEPOSTFIX 2>/dev/null | head -1)
 if [ -z "$GDB" ]; then
   panic "Can't find Android gdb client in your path, check your \
 --toolchain path."
 fi
 log "Host gdb client: $GDB"
 
 # Find gdbserver binary, we will later push it to /data/local/tmp
 # This ensures that both gdbserver and $GDB talk the same binary protocol,
 # otherwise weird problems will appear.
 #
@@ skipping 376 matching lines @@
   echo "### START $COMMANDS"
   cat $COMMANDS
   echo "### END $COMMANDS"
 fi
 
 log "Launching gdb client: $GDB $GDBARGS -x $COMMANDS"
 $GDB $GDBARGS -x $COMMANDS &&
 rm -f "$GDBSERVER_PIDFILE"
 
 clean_exit $?