Home
last modified time | relevance | path

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

/linux-4.1.27/scripts/
Dcheck_extable.sh9 objdump -hj __ex_table ${obj} 2> /dev/null > /dev/null
14 suspicious_relocs=$(objdump -rj __ex_table ${obj} | tail -n +6 |
32 …eval $(objdump -t ${obj} | grep ${1} | sed 's/\([0-9a-f]\+\) .\{7\} \([^ \t]\+\).*/section="\2"; s…
54 …eval $(objdump -rj .altinstructions ${obj} | grep -B1 "${section}+${section_offset}" | head -n1 | …
71 objdump -hwj ${section} ${obj} | grep -q CODE
133 objdump -hj .debug_info ${obj} 2> /dev/null > /dev/null ||
Drecordmcount.pl122 my ($arch, $endian, $bits, $objdump, $objcopy, $cc,
142 $objdump = 'objdump' if (!$objdump);
230 $objdump .= " -M x86-64";
240 $objdump .= " -M i386";
346 $objdump .= " -Melf-trad".$endian."mips ";
471 open(IN, "$objdump -hdr $inputfile|") || die "error running $objdump";
Dnamespace.pl70 my $objdump = ($ENV{'OBJDUMP'} || "objdump") . " -s -j .comment";
238 open(my $objdumpdata, "$objdump $basename|")
239 or die "$objdump $fullname failed $!\n";
Ddecodecode61 ${CROSS_COMPILE}objdump $OBJDUMPFLAGS -S $1.o | \
/linux-4.1.27/arch/powerpc/
Drelocs_check.sh22 objdump="$1"
26 "$objdump" -R "$vmlinux" |
/linux-4.1.27/tools/perf/Documentation/
Dperf-annotate.txt88 --disassembler-style=:: Set disassembler style for objdump.
90 --objdump=<path>::
91 Path to objdump binary.
Dperf-report.txt252 --disassembler-style=:: Set disassembler style for objdump.
284 --objdump=<path>::
285 Path to objdump binary.
Dperf-top.txt151 --disassembler-style=:: Set disassembler style for objdump.
/linux-4.1.27/arch/avr32/
DMakefile59 cmd_listing = avr32-linux-objdump $(OBJDUMPFLAGS) -lS $< > $@
61 cmd_disasm = avr32-linux-objdump $(OBJDUMPFLAGS) -d $< > $@
/linux-4.1.27/arch/x86/tools/
Dchkobjdump.awk11 /^GNU objdump/ {
/linux-4.1.27/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-4.1.27/arch/powerpc/boot/
Dwrapper338 membase=`${CROSS}objdump -p "$kernel" | grep -m 1 LOAD | awk '{print $7}'`
405 entry=`${CROSS}objdump -f "$ofile" | grep '^start address ' | cut -d' ' -f3`
/linux-4.1.27/Documentation/
DBUG-HUNTING152 To debug a kernel, use objdump and look for the hex offset from the crash
158 objdump -r -S -l --disassemble net/dccp/ipv4.o
180 > "objdump --disassemble foo.o".
Dkmemcheck.txt497 $ objdump -d --no-show-raw-insn vmlinux | grep -C 8 ffffffff8104ede8:
Dkprobes.txt321 so you can use "objdump -d -l vmlinux" to see the source-to-object
/linux-4.1.27/Documentation/trace/
Duprobetracer.txt97 # objdump -T /bin/zsh | grep -w zfree
Dftrace-design.txt240 details for how to locate the addresses of mcount call sites via objdump.
/linux-4.1.27/
DMakefile361 OBJDUMP = $(CROSS_COMPILE)objdump
/linux-4.1.27/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.