linux-yocto/scripts/faddr2line
Will Deacon 86bf86e19d scripts/faddr2line: Use LLVM addr2line and readelf if LLVM=1
GNU utilities cannot necessarily parse objects built by LLVM, which can
result in confusing errors when using 'faddr2line':

$ CROSS_COMPILE=aarch64-linux-gnu- ./scripts/faddr2line vmlinux do_one_initcall+0xf4/0x260
aarch64-linux-gnu-addr2line: vmlinux: unknown type [0x13] section `.relr.dyn'
aarch64-linux-gnu-addr2line: DWARF error: invalid or unhandled FORM value: 0x25
do_one_initcall+0xf4/0x260:
aarch64-linux-gnu-addr2line: vmlinux: unknown type [0x13] section `.relr.dyn'
aarch64-linux-gnu-addr2line: DWARF error: invalid or unhandled FORM value: 0x25
$x.73 at main.c:?

Although this can be worked around by setting CROSS_COMPILE to "llvm=-",
it's cleaner to follow the same syntax as the top-level Makefile and
accept LLVM= as an indication to use the llvm- tools, optionally
specifying their location or specific version number.

Suggested-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Will Deacon <will@kernel.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Link: https://lore.kernel.org/r/20231002165750.1661-3-will@kernel.org
Signed-off-by: Josh Poimboeuf <jpoimboe@kernel.org>
2023-10-23 08:36:33 -07:00

8.5 KiB
Executable File

#!/bin/bash

SPDX-License-Identifier: GPL-2.0

Translate stack dump function offsets.

addr2line doesn't work with KASLR addresses. This works similarly to

addr2line, but instead takes the 'func+0x123' format as input:

$ ./scripts/faddr2line ~/k/vmlinux meminfo_proc_show+0x5/0x568

meminfo_proc_show+0x5/0x568:

meminfo_proc_show at fs/proc/meminfo.c:27

If the address is part of an inlined function, the full inline call chain is

printed:

$ ./scripts/faddr2line ~/k/vmlinux native_write_msr+0x6/0x27

native_write_msr+0x6/0x27:

arch_static_branch at arch/x86/include/asm/msr.h:121

(inlined by) static_key_false at include/linux/jump_label.h:125

(inlined by) native_write_msr at arch/x86/include/asm/msr.h:125

The function size after the '/' in the input is optional, but recommended.

It's used to help disambiguate any duplicate symbol names, which can occur

rarely. If the size is omitted for a duplicate symbol then it's possible for

multiple code sites to be printed:

$ ./scripts/faddr2line ~/k/vmlinux raw_ioctl+0x5

raw_ioctl+0x5/0x20:

raw_ioctl at drivers/char/raw.c:122

raw_ioctl+0x5/0xb1:

raw_ioctl at net/ipv4/raw.c:876

Multiple addresses can be specified on a single command line:

$ ./scripts/faddr2line ~/k/vmlinux type_show+0x10/45 free_reserved_area+0x90

type_show+0x10/0x2d:

type_show at drivers/video/backlight/backlight.c:213

free_reserved_area+0x90/0x123:

free_reserved_area at mm/page_alloc.c:6429 (discriminator 2)

set -o errexit set -o nounset

usage() { echo "usage: faddr2line [--list]