llvm-6502/test/tools/llvm-objdump/out-of-section-sym.test

// Check that llvm-objdump does not attempt to disassemble symbols outside
// of section boundaries.
// RUN: llvm-objdump -d -t %p/Inputs/out-of-section-sym.elf-i386 | FileCheck %s

CHECK: Disassembly of section .text:
CHECK-NEXT: _start:
CHECK-NEXT:   10:  c3  retl
CHECK-NEXT: SYMBOL TABLE:
CHECK-NEXT: 00000000         *UND*  00000000
CHECK-NEXT: 00000010 l    d  .text  00000000 .text
CHECK-NEXT: 00000010         .text  00000000 _start
CHECK-NEXT: 00000020         .text  00000000 _fdata
CHECK-NEXT: 00000010         .text  00000000 _ftext
llvm-objdump: Do not attempt to disassemble symbols outside of section boundaries. It is possible to create an ELF executable where symbol from say .text section 'points' to the address outside the section boundaries. It does not have a sense to disassemble something outside the section. Without this fix llvm-objdump prints finite or infinite (depends on the executable file architecture) number of 'invalid instruction encoding' warnings. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@202083 91177308-0d34-0410-b5e6-96231b3b80d8 2014-02-24 22:12:11 +00:00			`// Check that llvm-objdump does not attempt to disassemble symbols outside`
			`// of section boundaries.`
			`// RUN: llvm-objdump -d -t %p/Inputs/out-of-section-sym.elf-i386 \| FileCheck %s`

			`CHECK: Disassembly of section .text:`
			`CHECK-NEXT: _start:`
			`CHECK-NEXT: 10: c3 retl`
			`CHECK-NEXT: SYMBOL TABLE:`
			`CHECK-NEXT: 00000000 UND 00000000`
			`CHECK-NEXT: 00000010 l d .text 00000000 .text`
			`CHECK-NEXT: 00000010 .text 00000000 _start`
			`CHECK-NEXT: 00000020 .text 00000000 _fdata`
			`CHECK-NEXT: 00000010 .text 00000000 _ftext`