[android-ndk-29b] How to use the SimplePerf script 'report_ etm. py'?

[qianwindz]

I used the reportay_etm.py script to parse ETM data, and have already configured binary_cache and ndk_path, but the result seems to be not mapped. How do I use this script?

Cycles: 0
NO_SYNC: trace is lost, possibly due to overflow.
NO_SYNC: trace is lost, possibly due to overflow.
New Context: EL1 (NONSECURE) 64-bit ctid: 23902 vmid: None
PID: 14479, TID: 23902, comm: unknown
ADDR_NACC: trace address 0xffffffc081168900 is not mapped!
Current timestamp: 6634975119943
Cycles: 0
Current timestamp: 6634975119944
NO_SYNC: trace is lost, possibly due to overflow.
New Context: EL1 (NONSECURE) 64-bit ctid: 25766 vmid: None
PID: 25764, TID: 25766, comm: unknown
ADDR_NACC: trace address 0xffffffc08115919c is not mapped!
Current timestamp: 6634975119945
Cycles: 0
NO_SYNC: trace is lost, possibly due to overflow.
New Context: EL1 (NONSECURE) 64-bit ctid: 25766 vmid: None
PID: 25764, TID: 25766, comm: unknown
ADDR_NACC: trace address 0xffffffc081159190 is not mapped!
Current timestamp: 6634975119946
Cycles: 0
NO_SYNC: trace is lost, possibly due to overflow.
New Context: EL0 (NONSECURE) 64-bit ctid: 13386 vmid: None
PID: 12983, TID: 13386, comm: unknown
ADDR_NACC: trace address 0x77f88b63a0 is not mapped!
Current timestamp: 6634975119946

[enh-google]

@yabinc

[yabinc]

ADDR_NACC for binaries you didn't provide in binary_cache is normal.

For debugging, you can first use simpleperf dump to dump all mmap records and build ids.
Then use the mmap records to manually convert an address (0x77f88b63a0) to a binary path.
Then look for the build id for that binary in simpleperf dump output. See if the build id matches the build_id of the binary you provided in binary_cache.
You can also add debug prints in the script to see if report_etm.py finds binaries correctly, for example in https://cs.android.com/android/platform/superproject/main/+/main:system/extras/simpleperf/scripts/report_etm.py;l=152.