We don't support python3 at all and python2.6 can only be used if the
user installs an extra package (OrderedDict [1]). Ask for python2
explicitly in the shebang line to resolve the python3 issues and print
some instructions to the user regarding python2.6 when that is used.

If the user insists on using python2.6, provide a command line
switch (--force-26) to skip the version check. To reduce clutter, don't
document this switch in the --help text but inform the user about its
existence when we error out due to the python2.6 check.

In order to even print an error message in python3 we have to first
ensure that our code is valid in python3, otherwise the interpreter
fails to even start executing our code (so we can't print any
messages). Use 2to3 to patch up some print statements, etc. Also fix
inconsistent whitespace, which is a syntax error on python3.

[1] https://pypi.python.org/pypi/ordereddict

Change-Id: Ie2c0a200e60ec90bf6cf49789f2cc75f181fa94b

Some common operations include getting the parent structure of some
embedded field as well as getting "sibling" fields within the parent
structure. Add some convenience methods to the gdbmi module (as well as
wrappers in the RamDump class) for this.

Change-Id: Ic65d7e60b930af8c73384a30b6b0dd84fb55f09c

After a crash, ramdumps may be collected for analysis. The ram
parser is a tool to aid in analysis of these dumps. The script
extracts useful information from the dumps to help with debugging.
Please see the README for full details.

Change-Id: I7795686a96bbfe246edf47d09e3f616131688429