Most of the cases were where a C++ file was being compiled with the C substitution. There were a few cases of the opposite though. LLDB seems to be the only real culprit in the LLVM codebase for these mismatches. Rest of the LLVM presumably sticks at least language-specific options in the common substitutions making the mistakes immediately apparent. I found these by using Clang frontend configuration files containing language-specific options for both C and C++ (e.g. `-std=c2y` and `-std=c++26`).
18 lines
607 B
C++
18 lines
607 B
C++
// Test for a bug where we crashed while processing a compressed debug_names
|
|
// section (use after free).
|
|
|
|
// REQUIRES: lld, zlib
|
|
|
|
// RUN: %clangxx -c -o %t.o --target=x86_64-pc-linux -gdwarf-5 -gpubnames %s
|
|
// RUN: ld.lld %t.o -o %t --compress-debug-sections=zlib
|
|
// RUN: llvm-readobj --sections %t | FileCheck %s --check-prefix NAMES
|
|
// RUN: lldb-test symbols --find=variable --name=foo %t | FileCheck %s
|
|
|
|
// NAMES: Name: .debug_names
|
|
|
|
// CHECK: Found 1 variables:
|
|
int foo;
|
|
// CHECK-DAG: name = "foo", type = {{.*}} (int), {{.*}} decl = debug-names-compressed.cpp:[[@LINE-1]]
|
|
|
|
extern "C" void _start() {}
|