Searched hist:"24778 dedd4c2ed35390d491c9f3538de7d2daf47" (Results 1 – 1 of 1) sorted by relevance
| /optee_os/scripts/ |
| H A D | symbolize.py | 24778dedd4c2ed35390d491c9f3538de7d2daf47 Wed Feb 12 13:48:03 UTC 2020 Jerome Forissier <jerome@forissier.org> symbolize.py: fix analysis of mixed 32/64 bit ftrace dumps
When an ftrace file that contains both user space and kernel space
calls is analyzed by symbolize.py, any address can be 32 or 64 bits.
For each address, the resolve() function first obtains the path to the
proper ELF file, then calls spawn_addr2line() to make sure we have a
process that is capable of resolving the address (i.e., either
arm-linux-gnueabihf-addr2line or aarch64-linux-gnu-addr2line).
spawn_addr2line() then calls arch_prefix() to obtain the tool's prefix.
Unfortunately, the ELF file is not supplied, so arch_prefix() assumes
that the first entry in the global list of files is suitable. While this
is true when symbolizing homogeneous dumps (i.e., kernel stacks or
TA + multiple libraries), it does not work for mixed ftrace logs.
This patch addresses the issue by adding the ELF file as an argument to
spawn_addr2line().
Signed-off-by: Jerome Forissier <jerome@forissier.org>
Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|