- Apr 07, 2014
-
-
Mitchel Humpherys authored
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
-
- Apr 04, 2014
-
-
Mitchel Humpherys authored
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
-
- Mar 13, 2014
-
-
Laura Abbott authored
Ram dumps are now being generated for 64-bit ramdumps. Update the parser to account for this. Change-Id: I54a354f39701ad96dd7b81010ec6c5989dd471ad
-
- Jan 27, 2014
-
-
Mitchel Humpherys authored
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
-
Mitchel Humpherys authored
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
-
- 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
-