21041c9292
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`).
38 lines
1023 B
C++
38 lines
1023 B
C++
// This tests a crash which occured under very specific circumstances. The
|
|
// interesting aspects of this test are:
|
|
// - we print a global variable from one compile unit
|
|
// - we are stopped in a member function of a class in a namespace
|
|
// - that namespace is also present in a third file, which also has a global
|
|
// variable
|
|
|
|
// UNSUPPORTED: system-darwin, system-windows
|
|
|
|
// RUN: %clangxx_host -c -gsplit-dwarf -g %s -o %t1.o -DONE
|
|
// RUN: %clangxx_host -c -gsplit-dwarf -g %s -o %t2.o -DTWO
|
|
// RUN: %clangxx_host -c -gsplit-dwarf -g %s -o %t3.o -DTHREE
|
|
// RUN: %clangxx_host %t1.o %t2.o %t3.o -o %t
|
|
// RUN: %lldb %t -o "br set -n foo" -o run -o "expression bool_in_first_cu" -o exit \
|
|
// RUN: | FileCheck %s
|
|
|
|
// CHECK: (lldb) expression bool_in_first_cu
|
|
// CHECK: (bool) $0 = true
|
|
|
|
|
|
#if defined(ONE)
|
|
bool bool_in_first_cu = true;
|
|
#elif defined(TWO)
|
|
bool bool_in_second_cu = true;
|
|
|
|
namespace NS {
|
|
void f() {}
|
|
}
|
|
#elif defined(THREE)
|
|
namespace NS {
|
|
struct S {
|
|
void foo() {}
|
|
};
|
|
}
|
|
|
|
int main() { NS::S().foo(); }
|
|
#endif
|