GDB support for Android in devtools' debugger.

README.md

Index: README.md
diff --git a/README.md b/README.md
index 25050a6c0e8d1031f68d0e3fe00dd2160a7fba90..f09cb78033025bfc6a97f2334190e7d9e1ad58c9 100644
--- a/README.md
+++ b/README.md
@@ -265,6 +265,14 @@ stack trace present in the device log:
 mojo/devtools/common/debugger device stack
 ```
 
+#### GDB support

[ppi, 2015/07/09 13:12:38]

"support" is redundant, let's just say "gdb" or "Attaching gdb"?

[etiennej, 2015/07/15 07:13:20]

Done.

+It is possible to inspect a Mojo Shell process using GDB. The `debugger` script
+can be used to launch GDB and attach it to a running shell process (android
+only):
+```
+mojo/devtools/common/debugger gdb attach

[ppi, 2015/07/09 13:12:38]

I just tried to do just that, and the process hanged:

$ mojo/devtools/common/debugger gdb attach


^CTraceback (most recent call last):
  File "mojo/devtools/common/debugger", line 259, in <module>
    sys.exit(main())
  File "mojo/devtools/common/debugger", line 256, in main
    return args.func(args)
  File "mojo/devtools/common/debugger", line 162, in _gdb_attach
    _GetDirAbove('depot_tools'), 'depot_tools', 'third_party', 'gsutil',
  File "mojo/devtools/common/debugger", line 26, in _GetDirAbove
    if dirname in os.listdir(path):
KeyboardInterrupt


There are two action items here:

 - could you make it work out of the box in the regular mojo checkout?
 - we probably want to have an explicit error message instead of infinite loop
if some directory / tool cannot be located

[etiennej, 2015/07/15 07:13:20]

I don't know how your "regular mojo checkout" differs from mine, it might be
worth investigating. In any case, we now have an explicit error message and no
more infinite loop.

+```
+
 ### Android set-up
 
 #### Adb