Several ways to parse dump

In the development debugging process, often encounter mobile phone/device crash or dump, memory dump is an important way to analyze the system Crash/dump

In the process of Qualcomm, if the device occurs dump, the log of the dump will be cached to a certain area, the user can use the individual tools to analyze log out, the following is the basic qcom on the basis of the introduction of several methods to obtain the dump log:

  1.t32 method

Trace32 Onlie software, linked to the motherboard/device, and then using the Jtag method can get to Log,t32 method suitable for qcom and MTK various platforms, the specific method can be Google T32 query, here is not the focus of T32 method 2. Using 

2 pst to get

After dump, the phone will enter a special port mode (DIAG. 9006 Port), the phone is not in the shutdown/standby state, when the Qpst Configuration is opened, the phone will automatically crawl dump log and exported. At the same time, can be found in the phone status bar, the phone is in the state of Sahara memory dump. As follows:

The corresponding folder is then stored in the specified Qpst directory, and the default directory is:

C:\Program files\qualcomm\qpst\ ....

In Qpst, DUMP LOG is where the output path is set. The storage path is:

Click on the Help menu, the second open Log File Directory, in the pop-up window opens the Sahara folder, where the Port_comx folder is the dump Log, note here port_com with the previous qpst Configu The ration software displays the COM number in the same order. To ensure this is the export
Note that the following are :

1. When the link qpst export, please relationship with other port-occupied software, such as QDST and so on, otherwise it may cause qpst unable to connect the serial

2.QPST software is best run under window, run in window of virtual machine sometimes unknown error link not

xxxxxxxx

Get to dump log, at this time the log is not directly review, also need to be processed, get ramdump+vmulinux, put in the same path

Script please download: linux-ramdump-parser-v2/ramparse.py

git clone git://codeaurora.org/quic/la/platform/vendor/qcom-opensource/tools

The above tools are required to distinguish between 32-bit and 64-bit , please note the environment

Also find the cross-compilation environment provided by the NDK in the Android environment: Arm-linux-androideabi-gdb and ARM-LINUX-ANDROIDEABI-NM (can also be downloaded online)

Execute the following cmd:

Python /data/doc/linux-ramdump-parser-v2/ramparse.py --force-hardware=8916 -v/data/port_ Com49/vmlinux -G /data/p445tf/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/ Arm-linux-androideabi-gdb-n/data/p445tf/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8/bin/ ARM-LINUX-ANDROIDEABI-NM -A/data/port_com49-o/DATA/DUMP8 –x

Above, red Section : ramparse.py script path

Green Section : Platform information

Light Purple section : Vmlinux path

Dark Purple part : cross-compilation environment path, the current path is the GCC environment is compiled and stored in the location

Dark black Section : Dump file name

The above is to illustrate the script usage, preferably added to the ~/brasch, convenient and quick

Where-v Specifies the kernel vmlinux file with debug information corresponding to the dump file
-g Specifies the corresponding GDB tool file
-o Specifies the output directory of the parsing file
-X indicates that all debug messages are output

After the command executes, the following parsing info will appear

!!! Out directory does not exist. Creating ...


[1/32]--clock-dump ... 0.873911s
[2/32]--cpr3-info ... 0.135361s
[3/32]--cpr-info ... 1.103903s
[4/32]--cpu-state ... 0.098867s
[5/32]--ddr-compare ... 3.923111s
[6/32]--check-for-watchdog ... 0.011697s
[7/32]--parse-debug-image ...
...

Wait about 8 minutes after the prompt parsing is complete, and then you can open the analysis, dump log all parse completed

3. Using Qualcomm Qcap website parsing

First, you have to have a Qualcomm account. You have to have a Qualcomm account. You have to have a Qualcomm account. (At the same time qcom there is your project information warehousing) important thing to say three times

QCAP website:

Https://cap.qti.qualcomm.com/default.aspx

After the entry is the following interface, the interface holds all of your parsed dump file records, and even can download the XML to help Qualcomm analysis

Then to use this Web tool, click on New start Analysas, will go to the following page:

Carsh log is the path to dump log, as the information on the graph is filled

and build location This selects the Contents.xml path, the file is stored under nonhlos/or amss/, used to distinguish the modem side of each partition of the information, according to this file will parse the corresponding log

The following interface is displayed when parsing is complete:

Home page will be automatically help analysis of root case, of course, the solution to the problem also need to go deep to see the detailed log (on the left side can see the tz,modem,ap side of the various types of log and storage stack information)

Strange is, the individual log local parsing will have an exception, no log spit, if there is case in qcom help analysis, qcom will want a copy of such vmlinux,dump file and so take to resolve (said they parse out the file is complete)