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`).
32 lines
842 B
Plaintext
32 lines
842 B
Plaintext
# XFAIL: target-windows
|
|
|
|
# Test that the plugin.cplusplus.display.function-name-format setting
|
|
# doesn't print into the frame-format setting unless all its format variables
|
|
# were successful.
|
|
|
|
# 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
|
|
|
|
#--- main.cpp
|
|
template<typename T> T gunc(int x = 10) {
|
|
return T{};
|
|
}
|
|
|
|
int main(int argc, const char *argv[]) {
|
|
gunc<int>();
|
|
return 0;
|
|
}
|
|
|
|
#--- commands.input
|
|
settings set plugin.cplusplus.display.function-name-format "${function.basename}${script.target:invalid_func}"
|
|
settings set -f frame-format "custom-frame '${function.name-with-args}'\n"
|
|
break set -l 2 -f main.cpp
|
|
|
|
run
|
|
bt
|
|
|
|
# CHECK: custom-frame 'int gunc<int>(x=10)'
|
|
# CHECK: custom-frame 'main(argc=1, argv={{.*}})'
|