Home
last modified time | relevance | path

Searched refs:objdump (Results 1 – 25 of 25) sorted by relevance

/Linux-v4.19/scripts/
Dcheck_extable.sh10 objdump -hj __ex_table ${obj} 2> /dev/null > /dev/null
15 suspicious_relocs=$(objdump -rj __ex_table ${obj} | tail -n +6 |
33 …eval $(objdump -t ${obj} | grep ${1} | sed 's/\([0-9a-f]\+\) .\{7\} \([^ \t]\+\).*/section="\2"; s…
55 …eval $(objdump -rj .altinstructions ${obj} | grep -B1 "${section}+${section_offset}" | head -n1 | …
72 objdump -hwj ${section} ${obj} | grep -q CODE
134 objdump -hj .debug_info ${obj} 2> /dev/null > /dev/null ||
Drecordmcount.pl123 my ($arch, $endian, $bits, $objdump, $objcopy, $cc,
146 $objdump = 'objdump' if (!$objdump);
234 $objdump .= " -M x86-64";
244 $objdump .= " -M i386";
366 $objdump .= " -Melf-trad".$endian."mips ";
491 open(IN, "$objdump -hdr $inputfile|") || die "error running $objdump";
Dnamespace.pl70 my $objdump = ($ENV{'OBJDUMP'} || "objdump") . " -s -j .comment";
240 open(my $objdumpdata, "$objdump $basename|")
241 or die "$objdump $fullname failed $!\n";
Ddecodecode82 ${CROSS_COMPILE}objdump $OBJDUMPFLAGS -S $1.o | \
/Linux-v4.19/arch/powerpc/tools/
Dunrel_branch_check.sh15 objdump="$1"
21 "$objdump" -R "$vmlinux" -d --start-address=0xc000000000000000 \
28 "$objdump" -R "$vmlinux" -D --start-address=0xc000000000000000 \
Drelocs_check.sh22 objdump="$1"
26 "$objdump" -R "$vmlinux" |
/Linux-v4.19/tools/perf/arch/x86/tests/
Dgen-insn-x86-dat.sh29 objdump -dSw insn-x86-dat-src.o | awk -f gen-insn-x86-dat.awk > insn-x86-dat-64.c
37 objdump -dSw insn-x86-dat-src.o | awk -f gen-insn-x86-dat.awk > insn-x86-dat-32.c
/Linux-v4.19/tools/perf/arch/arm/annotate/
Dinstructions.c52 arch->objdump.comment_char = ';'; in arm__annotate_init()
53 arch->objdump.skip_functions_char = '+'; in arm__annotate_init()
/Linux-v4.19/tools/perf/arch/arm64/annotate/
Dinstructions.c55 arch->objdump.comment_char = '/'; in arm64__annotate_init()
56 arch->objdump.skip_functions_char = '+'; in arm64__annotate_init()
/Linux-v4.19/tools/perf/Documentation/
Dperf-annotate.txt110 --disassembler-style=:: Set disassembler style for objdump.
112 --objdump=<path>::
113 Path to objdump binary.
Dperf-report.txt325 --disassembler-style=:: Set disassembler style for objdump.
357 --objdump=<path>::
358 Path to objdump binary.
Dperf-top.txt156 --disassembler-style=:: Set disassembler style for objdump.
/Linux-v4.19/arch/x86/tools/
Dchkobjdump.awk11 /^GNU objdump/ {
/Linux-v4.19/tools/perf/arch/s390/annotate/
Dinstructions.c25 if (arch->objdump.skip_functions_char && in s390_call__parse()
26 strchr(name, arch->objdump.skip_functions_char)) in s390_call__parse()
/Linux-v4.19/tools/perf/arch/powerpc/annotate/
Dinstructions.c57 arch->objdump.comment_char = '#'; in powerpc__annotate_init()
/Linux-v4.19/arch/powerpc/boot/
Dwrapper410 membase=`${CROSS}objdump -p "$kernel" | grep -m 1 LOAD | awk '{print $7}'`
478 entry=`${CROSS}objdump -f "$ofile" | grep '^start address ' | cut -d' ' -f3`
/Linux-v4.19/Documentation/x86/
Dexception-tables.txt159 > objdump --section-headers vmlinux
186 > objdump --disassemble --section=.text vmlinux
204 > objdump --disassemble --section=.fixup vmlinux
211 > objdump --full-contents --section=__ex_table vmlinux
/Linux-v4.19/Documentation/admin-guide/
Dbug-hunting.rst186 objdump subsection
189 To debug a kernel, use objdump and look for the hex offset from the crash
195 $ objdump -r -S -l --disassemble net/dccp/ipv4.o
219 "objdump --disassemble foo.o".
/Linux-v4.19/tools/perf/util/
Dannotate.c78 } objdump; member
158 .objdump = {
169 .objdump = {
224 if (arch->objdump.skip_functions_char && in call__parse()
225 strchr(name, arch->objdump.skip_functions_char)) in call__parse()
307 ops->raw_comment = strchr(ops->raw, arch->objdump.comment_char); in jump__parse()
518 comment = strchr(s, arch->objdump.comment_char); in mov__parse()
581 comment = strchr(s, arch->objdump.comment_char); in dec__parse()
/Linux-v4.19/tools/bpf/bpftool/bash-completion/
Dbpftool108 maps=$(objdump -j maps -t $obj 2>/dev/null | \
120 nmaps=$(objdump -j maps -t $obj 2>/dev/null | grep -c 'g . maps')
/Linux-v4.19/Documentation/trace/
Duprobetracer.rst106 # objdump -T /bin/zsh | grep -w zfree
Dftrace-design.rst265 details for how to locate the addresses of mcount call sites via objdump.
/Linux-v4.19/Documentation/s390/
DDebugging390.txt768 So if you have an objdump listing by hand, it is quite easy to follow, and if
769 you don't have an objdump listing keep a copy of the s/390 Reference Summary
957 1) objdump --syms <program to be debugged> | grep main
1891 help when using objdump --source.
/Linux-v4.19/
DMakefile379 OBJDUMP = $(CROSS_COMPILE)objdump
/Linux-v4.19/Documentation/
Dkprobes.txt342 so you can use "objdump -d -l vmlinux" to see the source-to-object