lldb/test/Shell/Settings/TestFrameFormatFunctionSuffix.test

# UNSUPPORTED: system-windows

# Test the ${function.suffix} frame-format variable.

# RUN: split-file %s %t
# RUN: %clang_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
void bar() asm("_Z3barv.cold");
void bar() {}

int main() { bar(); }

#--- commands.input
settings set -f frame-format "custom-frame '${function.suffix}'\n"
break set -n "_Z3barv.cold"

run
bt

# CHECK: custom-frame ' (.cold)'
[lldb][test] Skip TestFrameFormatFunctionSuffix.test on Windows We skip/xfail the other FrameFormat tests on Windows already. The number of different buildbot configurations out there targetting Windows makes it hard to make this test portable. If we want to test this on Windows we should probably just make a dedicated test for it. 2025-04-29 14:24:00 +01:00			`# UNSUPPORTED: system-windows`
[lldb][Format] Add function.suffix frame-format variable (#137763) This patch adds another frame-format variable (currently only implemented in the CPlusPlus language plugin) that represents the "suffix" of a function. The name is derived from the `DotSuffix` node of LLVM's Itanium demangler. For a function name such as `int foo() (.cold)`, the suffix would be `(.cold)`. 2025-04-29 10:02:44 +01:00
			`# Test the ${function.suffix} frame-format variable.`

			`# RUN: split-file %s %t`
			`# RUN: %clang_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`
			`void bar() asm("_Z3barv.cold");`
			`void bar() {}`

			`int main() { bar(); }`

			`#--- commands.input`
			`settings set -f frame-format "custom-frame '${function.suffix}'\n"`
			`break set -n "_Z3barv.cold"`

			`run`
			`bt`

			`# CHECK: custom-frame ' (.cold)'`