1# Use address that can't fit in a 64-bit number. Show that llvm-symbolizer 2# simply treats it as an unknown symbol. 3RUN: llvm-symbolizer --obj=%p/Inputs/addr.exe 0x10000000000000000 | FileCheck --check-prefix=LARGE-ADDR %s 4 5LARGE-ADDR-NOT: {{.}} 6LARGE-ADDR: ?? 7LARGE-ADDR-NEXT: ??:0:0 8LARGE-ADDR-EMPTY: 9LARGE-ADDR-NOT: {{.}} 10 11RUN: echo '"some text"' '"some text2"' > %t.rsp 12RUN: echo -e 'some text\nsome text2\n' > %t.inp 13 14# Test bad input address values, via stdin, command line and response file. 15RUN: llvm-symbolizer --obj=%p/Inputs/addr.exe < %t.inp | FileCheck --check-prefix=BAD-INPUT %s 16RUN: llvm-symbolizer --obj=%p/Inputs/addr.exe "some text" "some text2" | FileCheck --check-prefix=BAD-INPUT %s 17RUN: llvm-symbolizer --obj=%p/Inputs/addr.exe @%t.rsp | FileCheck --check-prefix=BAD-INPUT %s 18 19# Test bad input address values for the GNU-compatible version. 20RUN: llvm-addr2line --obj=%p/Inputs/addr.exe < %t.inp | FileCheck --check-prefix=BAD-INPUT %s 21RUN: llvm-addr2line --obj=%p/Inputs/addr.exe "some text" "some text2" | FileCheck --check-prefix=BAD-INPUT %s 22RUN: llvm-addr2line --obj=%p/Inputs/addr.exe @%t.rsp | FileCheck --check-prefix=BAD-INPUT %s 23 24BAD-INPUT: ?? 25BAD-INPUT-NEXT: ??:0 26