- Mar 12, 2014
-
-
Laura Abbott authored
The PAGE_OFFSET (traditionally 0xc0000000) may change depending on architecture version. Switch it to be a property of the ramdump. Change-Id: Ide04649f59005f39e84d0caa5edab0f46e691b3f
-
Laura Abbott authored
unwind tables may not be used on all dumps. Support unwinding the old fashioned way with framepointers. Change-Id: I978c604dc0974eb6930249e47a205e3d9d37c249
-
Laura Abbott authored
Several of the fields of the task are not being read out as 'true size'. Use more appropriate functions. At the same time, factor out the reading of pc/fc/sp into a ramdump specific functionality since that code may be architectur specific. Change-Id: I5d7bd14031a4431aa665207e8e31e3ecb7dd1cdb
-
Laura Abbott authored
When tracing with read_physical, the result of what was read is printed. The result may contain unprintable characters which wreak havok on terminals. re-use the cleanupString function which is already in use in several places to make the output readable. Change-Id: I1a62c88f1d51038ba2c429d8ec918c58d39af4bf
-
Laura Abbott authored
The return size of read_word may change depending on the architecture. Add functions to read specific types and sizes. Change-Id: I3b9b11c263bf684a8e3783a10dcdc770a6a1b25e
-
- Mar 10, 2014
-
-
Laura Abbott authored
When reading soc info, the ram information has not yet been fully plumbed into the parser (this is very early!). We should not take the address for the start of ram into account at this point as smem should only be given as an offset. Update the calculations. Change-Id: Ib02db2f118685b306457e2591e4bbc5f19f2edbc
-
Laura Abbott authored
When adding a new board, it can be non-obvious what went wrong if the board is not immediately detected. Add an option to trace through socinfo addresses for a specific board to print out useful addresses as a debugging aid. Also clean up some error handling, mostly among the tracing code. Change-Id: I65f4a38b95912b81676f44cd371751abc96aae9e
-
- Feb 27, 2014
-
-
Laura Abbott authored
A recent build has generated multiple badly corrupted dumps. Fix all the errors found by the unintentional fuzzing. Change-Id: I0854bee4558d31037f51ed2ea941eb58997607c8
-
- Feb 13, 2014
-
-
Laura Abbott authored
The specification of boards of the parser is not very clean. Re-write it into an easier to read fashion. Change-Id: Icae5b8421cf574ee910e4702fcf14d29378ed703
-
- Jan 03, 2014
-
-
Laura Abbott authored
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
-