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`).
31 lines
720 B
Plaintext
31 lines
720 B
Plaintext
# XFAIL: target-windows
|
|
|
|
# Test the ${function.qualifiers} frame-format variable.
|
|
|
|
# RUN: split-file %s %t
|
|
# RUN: %clangxx_host -g -gdwarf %t/main.cpp -o %t.out
|
|
# RUN: %lldb -x -b -s %t/commands.input %t.out -o exit 2>&1 \
|
|
# RUN: | FileCheck %s
|
|
#
|
|
# RUN: %clangxx_host -O0 %t/main.cpp -o %t-nodebug.out
|
|
# RUN: %lldb -x -b -s %t/commands.input %t-nodebug.out -o exit 2>&1 \
|
|
# RUN: | FileCheck %s
|
|
|
|
#--- main.cpp
|
|
struct Foo {
|
|
void foo() const volatile && {}
|
|
void bar() { Foo{}.foo(); }
|
|
};
|
|
|
|
int main() { Foo{}.bar(); }
|
|
|
|
#--- commands.input
|
|
settings set -f frame-format "custom-frame '${function.qualifiers}'\n"
|
|
break set -n foo
|
|
|
|
run
|
|
bt
|
|
|
|
# CHECK: custom-frame ' const volatile &&'
|
|
# CHECK: custom-frame ''
|