Currently the registered parsers can be run in basically any order. It
would be slightly messy to run them in the order the user specified on
the command line, so just run them alphabetically for now.

This is needed to do regression testing on the LRDP (diff'ing output of
the same dumps with different LRDP code).

Change-Id: Ib63c9b5fecaf1170df0e9e121980fcd0e4f35623

A debug print statement snuck through at some point. Remove it.

Change-Id: Ifca4f54c1b65deaa06295be5422bd211be5405b0

To generate proper simulator launching scripts, the TTBR needs
to be set in the MMU object. This was missing for LPAE page tables.
Set it.

Change-Id: I236df9db59290e4fe90c1959a9a92b51622c821e

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

arm64 needs different parameters to read ramdumps. Update the script.

Change-Id: I33a79d5f98a0fdc271fa769ccd40aad495c677af

Add support to locate TMC trace buffer in memory when the
address width is greater than 32 bits.

Change-Id: I7d916a6f9cfe0312764702b67d410778eaa55a04

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

APQ8026 LW has a different memory map and the SMEM location
has moved to 0x0300_0000.

Change-Id: Iede7dc26f5dc11127a5ba7f8ce4288ec5ab85f2d

Add support to the ramdump parser to parse debug image v2
format. Current support is for parsing cpu context and QDSS
dumps.

Change-Id: Ic7437e3b999845d607366bcf727f00078f81915a

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

ListWalker.__init__ was recently changed to remove some unneeded
arguments. The vmalloc parser was also updated at roughly the same time
with a new usage of the ListWalker class and was using the old
constructor. Update it.

Change-Id: Ia47c22511aab7207b65813d25c9f97d65c24e2db

It's not always useful to pass extra data to the list walker function.
For example, if the list walker function is a class method, state can be
passed around by simply modifying class instance variables. Update
`ListWalker.walk' to accept extra arguments optionally, not require
them.

Change-Id: I433f1e34db5c143c838f0eb2ed7f58203712ccb3

The parser now requires Python 2.7 so that 2.7-specific features can be
leveraged. Update the README to reflect this.

Change-Id: I7e1ba9f99f077c7f48ed7b44ab24f56f0f18c3ea

[29d3f2ed: "lrdp-v2: refactor Iommu domain parsing code"] introduced
an extra argument for rb_tree `walker' functions, but didn't update the
runqueue rb_tree user, so the ramdump parser currently fails to print
the runqueue state. Fix this.

For certain dumps, before this change we would see the following
backtrace:

    Traceback (most recent call last):
      File "ramparse.py", line 266, in <module>
        p.cls(dump).parse()
      File "parsers/runqueue.py", line 196, in parse
        self.print_cfs_state(cfs_rq_addr)
      File "parsers/runqueue.py", line 101, in print_cfs_state
        rb_walker.walk(tasks_timeline_addr, self.cfs_node_func)
      File "rb_tree.py", line 54, in walk
        self._walk(node, func, [], extra)
      File "rb_tree.py", line 39, in _walk
        self._walk(left_node, func, seen, extra)
      File "rb_tree.py", line 39, in _walk
        self._walk(left_node, func, seen, extra)
      File "rb_tree.py", line 41, in _walk
        func(node, extra)
    TypeError: cfs_node_func() takes exactly 2 arguments (3 given)

Change-Id: Ic19ec42d6cfbe87b6e0a0e99c6adf7c41e5b35e9

Because pages are constantly being allocated and freed, the pagetypeinfo
may not be in a consistent state when dumps are collected. Check
to make sure there are no cycles in the list for more than just the
next item.

Change-Id: Ie986bbb78f39923dbe11ef0446912518bc6c7fc5

Sizes for 64-bit are different. Update rtb accordingly.

Change-Id: Ie7c4014cc22b7c071017bb3d76519542ba58082d

It's bothersome at a fundamental level that the first line of the
stack trace is printed out on the same line as the 'Stack:' tag.
Fix it.

Change-Id: I895ad0969c4afb5b081ad10dca180a2bb1178291