Use elf header to decide vmlinux is 32 or 64 bits instead of parameter

Change-Id: Id2f68fc58160e259a011247b6cbfd4efa9dab5e4

When LRDP-v2 starts to parse RAM dumps, it will initialize pipes
to gdb instance, but on exit, the same pipes are not closed due
to __del__ is not invoked in ramdump.py. This will cause the
python environment raising the following exception, which will
not be handled by LRDP-v2 after it's unloaded:

close failed in file object destructor:
sys.excepthook is missing
lost sys.stderr

Add explicit gdbmi closure when RamDump instance is not used any
more, to avoid the unhandled exception.

Change-Id: I7cebd1418440ba56f9d7c4374286a5b088d948dc

Current Linux Ram Dump Paser scripts are only able to load kernel
symbols by default. No loadable modules' symbols will be parsed
at startup time, which may result in 'unknown symbols' in some
cases, especially when checking SLAB info on dual-wifi platforms.

With this change, loadable modules' symbols can be parsed on
script startup by the following configurations:

1) Put all symbols under a certain dir, such as:

<dump_location>/symbols/wlan.ko
<dump_location>/symbols/wlan_sdio.ko

2) Add --sym_path when invoking the scripts, such as:

python %RAM_DUMP_PARSER_PATH%\ramparse.py --sym_path
<dump_location>/symbols

With the above actions, all loadable modules' symbols will be
parsed and stored for subsequent information dumping. Symbol
loading commands will also be added into the Trace32 startup
script.

Change-Id: Idda9c9a08cfd24c19bf4021e80fee5187cd031b9

	A minidump supports fewer features than a full ramdump,
	but does not require the user to save all 4GB+ of memory.
	Instead a small subset of DDR is saved by crashscope as an elf file.
	Currently dmesg logs, rtb logs, and the cpu context parser are supported.

	Example usage: python ramparse.py --vmlinux <vmlinux> --minidump
			--ram-elf <elf_file> --ram-file <OCIMEM.bin> --everything

Change-Id: Ib689b4811d66472ac20aa7c63893fdaed915512e

   This changes to fetch serila number of HW from dump

Change-Id: I93ee37feafd9e407fe380761c0e6469fabe40f7d

Customers normally share extracted logs from RAMDUMP because of
various reasons including security and to protect personal
information. Add support to extract WLAN module debug details so
that customer issues can be triaged easily.

CRs-fixed: 1074311
Change-Id: If7a3f2c6ed990d9203ea93c8e0688c5c44f13c53

The board number is intended to be a human readable identification value.
Allowing this to be a string is more flexible.

CRs-Fixed: 1013327
Change-Id: If523acafc54f5026680d18c95e4899fb0436599d

Debug image parsing currently includes QDSS ETM and ETR binary data
parsing by default. However, these two parsing operations can take a
significant amount of time if either of their respective data buffers
are very large. Furthermore, this binary data is not needed for most
common debug image parsing use cases.

Add an argument to optionally disable QDSS ETM and ETR binary data
parsing when debug image parsing has also been selected.

Change-Id: Iab25c15d00dde1bb5dfafb3149e6e55760fd6291

Add '--kaslr-offset' option.  This specifies the offset for loading symbols
for a KASLR-enabled kernel.

Change-Id: I208d964ea3ca58536a0b80a32b4e334c73aae534

Although the `--shell' option can currently be used for ad-hoc
debugging, it's not ideal for scripting since it prints out a bunch of
other stuff during initialization.  Add a dedicated `--eval' option that
executes arbitrary Python code without printing anything else.

Change-Id: I9e24e6d140dd49208b850b2a17ac2f599a35657b

Most new targets are now 64-bit.  Make --64-bit the default and add a
--32-bit option to force 32-bit parsing.

Change-Id: I8b77b9851b714a4708bcd34c563a84119900fb07

Integrate the IPC Logging extraction script module into
linux-ramdump-parser-v2.

Move ipc_logging.py from into the linux-ramdump-parser-v2/parsers
directory, and create a relative symbolic link in the original location.
Add a new file, ipc_logging_ramparse.py, which performs the actual
integration.

Change-Id: If0db4f82814a644094af7ebd0e4290dd145f94ac

The constructor currently used in ramparse.py to initialize the RamDump
object has a very long argument list. This list can be shortened by
passing the options object to the constructor, rather than enumerating
every member of the options object as a separate argument.

Pass the options object to the RamDump constructor instead of passing
each member as a separate argument.

Change-Id: I7cbf173232838dd8f9fdbdad0e2b7336ad8fc07b

Currently we only generate scripts that work on t32 on Windows. Add
support for launcher scripts targeting t32 on Linux.

Change-Id: I50a293925e181f1b2370d6f7b0df719facdce18a

Add support to collect ftrace formats file and parse trace data
using QTF tool.

Change-Id: I6bd7dda1a39a60f714549dd22fabf11db00020e1

DDRCompare currently performs these tasks:
* Checks the magic values of all the statically initialized locks
* Scans the doubly linked list of the task list to find corruptions

Change-Id: Ie4904c2434f073d5711bb439029ffec35919846e

Some binaries may be compiled with a different page offset. Add
an option to allow the page offset to be adjusted properly.

Change-Id: I50cf0241f8a52aa0f9cd070da827775b5cb4764c

Sometimes it's useful to force a flush of the global outfile. Provide a
method to do so and use it in the main parser loop.

Change-Id: I18e9a07345c852d498b131b442df5a0c95bbcf98

It can be useful to know which parser is currently running and
how long each parser takes to run. Add some progress status
reporting to this end.

Change-Id: Ifc063feb4769fee02f0622d7a2c5ddf176ae00dc

For reasons ranging from mangled dumps to bugs in code, the parser may
generate exceptions while parsing. Rather than terminate the entire
script, handle exceptions in a more graceful fashion.

Change-Id: I883ee9c0910802b00c797380af5b21e00990dce8

If the user has python2.7 installed but it's not the default interpreter
on their system, they might get confused when they invoke the parser and
get a message about needing to install 2.7 even though they already have
it installed. Add some instructional messages about this situation to
the 2.6 invocation warning message as well as the README.

Change-Id: Ib1ee7df39199f715b236dbda2f75093ba0501648

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