Currently we split each config line on the equals sign, assuming that
there's only one equals sign there.  This isn't a valid assumption for
cases like:

    CONFIG_CMDLINE="console=ttyAMA0"

Fix this by splitting at the first equals sign, rather than splitting
at *all* equals signs.

Change-Id: I01e44fe2e9a0f09a8bebdd76715002f6b12cf0b5

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

Change-Id: I208d964ea3ca58536a0b80a32b4e334c73aae534

Some of our module documentation is a bit lacking.  Fix this by filling
in some docstrings and add then adding some pointers to existing
modules/functions in the docs.

Change-Id: Ibf714225f1fc185be916e514861540fd98cb2de5

Most read functions that take a virtual address also understand string
variable names, for convenience.  Add this support to the `hexdump'
function as well.

Change-Id: I773992ba3793a68226b49525b66141b021924387

Most of the time 100 is a good default max length when reading any old
C-string.  Use it.

Change-Id: I1805b0b4b2b9bc18c06f4ca0e7cd6cd70b854620

GdbMI.symbol_at returns a string, not a GdbSymbol object, so the extra
field traversal is unnecessary.

Change-Id: I85acd83657e4b6055bd1f7945da73dcf9d4839f1

The name symbol_at gives a better idea of what the function does, and it
more closely mirrors the corresponding gdbmi function.

Change-Id: If2f3df505bc129a3b963ea363e4c544599626948

In lieu of a more generic way of reading fields from structures,
introduce another specialized structure field reader for reading C
strings.

Change-Id: I6aba392f59179fa70a065a08f19a694e87f683dd

Rename addr_lookup to address_of to match common terminology more
closely.

Change-Id: I7fc744ce88d1f8880f13dfbf83fb0efcbe9ba0f2

Pointers can be either 32-bits or 64-bits, depending on the
architecture.  Add an accessor function to abstract this away.

Change-Id: I64e2c18c85ec3d9ca7304163dc5a42edc83f1443

A few reader functions currently assume that a virtual address (a
number) was passed in, but those functions also support reading variable
names.  Resolve the address or name to a virtual address before doing
arithmetic on it.

Change-Id: I55aa649ff203926565f8eaf3cb234677ef6b6104

Some of the return sequences in the memory accessor code are
unnecessarily complex.  Simplify them.

Change-Id: Iefe489b3ce4a4591574a2cc8d51aa23ce425b2b1

Currently there are "trace" print statements scattered throughout the
code.  These make the code harder to follow and aren't terribly useful.
Remove them in favor of on-demand instrumentation or more sophisticated
debugging methods (like a debugger).

Change-Id: I70a91b8dca34566d48ed1f4902cba5b9f9b4de40

The memory accessor functions that have documentation are using comments
rather than docstrings.  Fix this.  Also rename some variables for
improved self-documentation.

Change-Id: I6a196ff27665c5b0c96b3c5095b39690015b07e1

It can be useful to look up the values of config items.  Store a
dictionary mapping config options to their values.

Change-Id: I99f7615b2c5926558dfba100fa0c45b6e29ecdb5

Presently auto-dump option finds DDR base addresses from
statically defined per target meta data in boards.py. This
leads to auto-dump feature fail on different targets, say
with different DDR base and size.

Add support to parse DDR base addresses from load.cmm,
dump_info.txt or ramdump_msg.txt which ever is available in
that order. Fall-back to conventional static populated data
in boards.py if none of them is available.

Change-Id: Ie4ac4f281e92c9b527de17fa665c9cd6c3d5d384

The ram_dump.kernel_version variable is defined as a list and
incorrectly compared with tuple. This comparison always fails.
Fix it by changing ram_dump.kernel_version variable to tuple.

Change-Id: I12d4556693101fccfad795e5ea737b42e96acac7

Ram dump parser does not support unwinding the stack for NON
HLOS images. In certain cases, we get below exception when
parser tries to dump the context for NON HLOS address. Check
for NON HLOS address and return from the function without
unwinding the frame pointer.

Exception: Invalid stage 1 first- or second-level translation
descriptor: (value: 0x0 {dtype[1:0]=>0x0})
addr: (value: 0x21812010 {base[47:12]=>0x21812, offset[11:3]=>0x2})

Change-Id: I6cacec18574737d0e8261ba1f39dfe2b9b302304

Add support to parse DCC captured data from crash dumps and produce
human readable result.

Change-Id: I898b404b074fc037e339bf535c27bf190619cc9d

`major' is a bit of a misnomer, since the variable also includes the
minor version and patch version.  Rename it to `kernel_version'.

Change-Id: Ic567131c7f12ab03c9dea2716242e9053c17372f

In 3.18 kernel there is a slight change in radix_tree_node structure.
Fix irq parser to read radix_tree_node according to kernel version.

Change-Id: Ib9e67d137994f4b7424acd2b44676dcdcdb2d0a4

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

Do not use hardcoded value for TTBR1. Compute TTBR1 value using
swapper_pg_dir_addr and phys_offset variables dynamically.

Change-Id: Ia9b4704b07e933c686e366ed0af8230be1d97e9c

Running launch_t32.bat with newer T32 gives syntax errors without newlines
before "SCREEN=" and "PRINTER=WINDOWS" strings in t32_config.t32. Add
newlines before these strings to avoid T32 syntax errors.

Change-Id: I53ffd02d4c86959804a89bd744bf1ce7f42f163c

If user specified --force-hardware, then skip the socinfo parsing to
determine the hardware/board information. The user is warned about
using the force-hardware option any way.

Checking for valid swapper_pg_dir in the vmlinux also ensures that
the parsing doesn't trip over when --force-hardware is used along with
a bad or stripped vmlinux.

Change-Id: Icce1556b39a7533418668a7f38af30f4463c32e5

Add a parser which parses relevant CPR regulator information
such as target quotient, enable flag and most recent voltage for
each registered cpr regulator.

Change-Id: I15432179a0cfd76575236be9c276f83a8ef7124e

T32 simulator sessions currently launched from lrdp shortcuts do not
contain anything that allows separate sessions to be distinguished
from one another. Add a line that updates the titlebar of any launched
t32 simulator session with the full path to the RAM dumps being loaded
in the session.

Change-Id: I4273b4f000c96ed13af897dd23c0cd19b36c9a80

hexdump currently prints to stdout.  Although that's convenient for
interactive debugging it's not very useful for re-use in other parts of
the parser.  Return a string instead of printing to stdout.

Also add a usage example.

Change-Id: I18535f5339be85ffc5661e51430bba9a55fe665d

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

Change-Id: I50a293925e181f1b2370d6f7b0df719facdce18a

Currently our generated t32 launcher script always uses port 20,000 for
intercom. This prevents end users from launching two instances of t32
without hacking up the config file by hand. Randomize the port number to
avoid this (there will still be a chance of collision, but it should be
negligible).

Change-Id: Ia6f63a69e0ed315ac08c58d9903c2d1ef34b6c69

T32 is a powerful tool which has some advanced features for remote
access and the like. Add a few T32 options to t32_config.t32 to
let this work.

Change-Id: I158e16208b679689e677f1025efe964e89a8bfd6

Fix the t32 tool path for 8939 and 8936, and fix the cpu type in
startup script.

Change-Id: Ia1b7af9f80f2fb46a2b3c964630aecfe8b82e80a

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

Add support for t32 mmu config for 8994 since it is different
from 8916/8939.

Change-Id: I2e666f50d34187ae259e35e4b941669c984132aa

Fix the cpu values for 8916, 8939 and 8994 so that the cpu_type
used while creating the t32_startup_script.cmm is correct.

Change-Id: Ib43aebebde5492a3aa6cbf39467ccae8a94a5fe7

Add autodump parsing support for DDR sizes greater than 2GB.

Change-Id: I9b008d08612f08fdbc9ec486e08fc6b00e7d3357

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

Commit 4eb3aa20
(linux-ramdump-parser-v2: Update RTB for 64-bit) added support for
64-bit RTB parsing but broke backwards compatibility for old branches
that don't have the 64-bit changes. Update the parser to support
both old and new formats.

Change-Id: I6b9d834e1073d97dd3ffe43c1cc1f753d40e91b8