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

Currently, if the user doesn't specify a vmlinux image or an
autodumpdir (like when running ramparse.py with absolutely no arguments)
they get a big ugly python stacktrace and no helpful error message. Fix
this.

Change-Id: I2d5aaaae5c8afd651ef48cfbd8f974227c2032fe

Currently we error out and ask the user to create the output directory
if it doesn't exist. As a convenience, just create the directory for
them.

Change-Id: I0e9caa8294d644621bd166a06e2a70c8ca5715fc

It's not uncommon for the vmlinux file to live in the same directory as
the actual RAM dumps. If the users doesn't explicitly specify a vmlinux
image to use, look for it in the autodump dir. If we still can't find it
there, error out as usual.

Change-Id: I702c5584477e26912e0857dbd03b02491bd33c6c

When local_settings.py is missing variables we just error out when
trying to access those attributes. Improve the error message by
mentioning local_settings.py and pointing the user to README.txt.

Change-Id: Iaa2a1ab96ca889d75972bbfa1d4e127a8bf5bec1

During development, it's quite convenient to load up an interactive
python interpreter with a RamDump instance loaded. Add some command line
switches to launch an interactive shell with the RamDump instance that
gets created as a result of whatever other command line options are
passed.

If IPython is installed, an IPython interpreter will be launched,
otherwise a classic Python interpreter will be launched. The classic
interface can also be forced with --classic-shell.

Change-Id: Id59acb97a830055212de9db3eaf05f18358f757f

Ram dumps are now being generated for 64-bit ramdumps. Update the
parser to account for this.

Change-Id: I54a354f39701ad96dd7b81010ec6c5989dd471ad

Somewhere along the way we started ignoring the --nm-path and --gdb-path
options. Fix this. Also ensure that the command line options take
precedence over anything from local_settings.py or anything discovered
from CROSS_COMPILE.

Change-Id: I39ff653c7de7fb1de170701b898567c9b2356835

We are currently printing gdb_path when there are issues with
nm_path. Fix this by printing nm_path. Also change local_settings.pyi to
local_settings.py.

Change-Id: I391abb423b32cf571be1d6da3b8961cc3c6e2ee4

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