llvm-mirror/test/DebugInfo/symbolize.test

RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x40113f" > %t.input
RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x401020" >> %t.input
RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x40110e" >> %t.input
RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x401160" >> %t.input
RUN: echo "%p/Inputs/dwarfdump-test2.elf-x86-64 0x4004e8" >> %t.input
RUN: echo "%p/Inputs/dwarfdump-test2.elf-x86-64 0x4004f4" >> %t.input
RUN: echo "%p/Inputs/dwarfdump-test4.elf-x86-64 0x62c" >> %t.input

RUN: llvm-symbolizer < %t.input | FileCheck %s

CHECK:       main
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:16

CHECK:      _start

CHECK:      f(int, int)
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:11

CHECK:      DummyClass
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:4

CHECK:      a
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test2-helper.cc:2

CHECK:      main
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test2-main.cc:4

CHECK:      c()
CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test4-part1.cc:2
Reapply: DebugInfo: Assume an absence of ranges or high_pc on a CU means the CU is empty (devoid of code addresses) Originally committed in r349333, reverted in r349353. GCC emitted these unconditionally on/before 4.4/March 2012 Clang emitted these unconditionally on/before 3.5/March 2014 This improves performance when parsing CUs (especially those using split DWARF) that contain no code ranges (such as the mini CUs that may be created by ThinLTO importing - though generally they should be/are avoided, especially for Split DWARF because it produces a lot of very small CUs, which don't scale well in a bunch of other ways too (including size)). The revert was due to a (Google internal) test that had some checked in old object files missing DW_AT_ranges. That's since been fixed. llvm-svn: 349968 2018-12-21 23:25:01 +01:00			`RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x40113f" > %t.input`
			`RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x401020" >> %t.input`
			`RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x40110e" >> %t.input`
			`RUN: echo "%p/Inputs/dwarfdump-test.elf-x86-64 0x401160" >> %t.input`
Revert changes in r310953 for llvm-symbolizer.test. The change causes a test failure. llvm-svn: 310956 2017-08-15 23:02:17 +02:00			`RUN: echo "%p/Inputs/dwarfdump-test2.elf-x86-64 0x4004e8" >> %t.input`
			`RUN: echo "%p/Inputs/dwarfdump-test2.elf-x86-64 0x4004f4" >> %t.input`
			`RUN: echo "%p/Inputs/dwarfdump-test4.elf-x86-64 0x62c" >> %t.input`
Add a basic test for llvm-symbolizer tool llvm-svn: 178858 2013-04-05 10:30:13 +02:00
[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`RUN: llvm-symbolizer < %t.input \| FileCheck %s`
llvm-symbolizer: prefer .dwo contents over fission-gmlt-like-data when .dwo file is present Rather than relying on the gmlt-like data emitted into the .o/executable which only contains the simple name of any inlined functions, use the .dwo file if present. Test symbolication with/without a .dwo, and the old test that was testing behavior when no gmlt-like data was present. (I haven't included a test of non-gmlt-like data + no .dwo (that would be akin to symbolication with no debug info) but we could add one for completeness) The test was simplified a bit to be a little clearer (unoptimized, force inline, using a function call as the inlined entity) and regenerated with ToT clang. For the no-gmlt-like-data case, I modified Clang back to its old behavior temporarily & the .dwo file is identical so it is shared between the two executables. llvm-svn: 267227 2016-04-22 23:32:59 +02:00
Add a basic test for llvm-symbolizer tool llvm-svn: 178858 2013-04-05 10:30:13 +02:00			`CHECK: main`
			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:16`
[llvm-symbolizer] Avoid calling slow getSymbolSize for Mach-O files. Assume that symbols with zero size are in fact large enough. llvm-svn: 183213 2013-06-04 09:57:38 +02:00
			`CHECK: _start`

[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`CHECK: f(int, int)`
Kill symbolization functionality in llvm-dwarfdump. We have llvm-symbolizer for that. llvm-svn: 209152 2014-05-19 20:45:32 +02:00			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:11`

[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`CHECK: DummyClass`
Kill symbolization functionality in llvm-dwarfdump. We have llvm-symbolizer for that. llvm-svn: 209152 2014-05-19 20:45:32 +02:00			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test.cc:4`

[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`CHECK: a`
Kill symbolization functionality in llvm-dwarfdump. We have llvm-symbolizer for that. llvm-svn: 209152 2014-05-19 20:45:32 +02:00			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test2-helper.cc:2`

[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`CHECK: main`
Kill symbolization functionality in llvm-dwarfdump. We have llvm-symbolizer for that. llvm-svn: 209152 2014-05-19 20:45:32 +02:00			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test2-main.cc:4`

[llvm-symbolizer][test] Rename and tweak tests using llvm-symbolizer Prior to this change, there are a few tests called llvm-symbolizer* in the DebugInfo test area. These really were testing either the DebugInfo or Symbolizer library, rather than the llvm-symbolizer tool itself, so this patch renames them to be clearer that they aren't explicitly tests for llvm-symbolizer (such tests belong in test/tools/llvm-symbolizer). This patch also reinstates the copying of a DWO file, removed previously in r352752. The test needs this so that it could possibly fail. Finally, some of the tests have been simplified slightly by removing unnecessary switches and/or unused check-prefixes. Reviewed by: dblaikie Differential Revision: https://reviews.llvm.org/D57518 llvm-svn: 352847 2019-02-01 11:24:55 +01:00			`CHECK: c()`
Add a basic test for llvm-symbolizer tool llvm-svn: 178858 2013-04-05 10:30:13 +02:00			`CHECK-NEXT: /tmp/dbginfo{{[/\\]}}dwarfdump-test4-part1.cc:2`