================
@@ -0,0 +1,54 @@
+"""
+Test that we can backtrace through an OUTLINED_FUNCTION which is called in a
non-ABI way.
+"""
+
+import lldb
+import json
+from lldbsuite.test.decorators import *
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test import lldbutil
+
+
+class TestBacktraceThroughOutlinedFunction(TestBase):
+ NO_DEBUG_INFO_TESTCASE = True
+
+ @skipIfLLVMTargetMissing("AArch64")
+ def test_backtrace_through_outlined_epilogue(self):
+ """Test that we can backtrace through an OUTLINED_FUNCTION that has
the epilogue of a function."""
----------------
jasonmolenda wrote:
I wanted to have at least one test that could be run on all platforms. I'll
change the test to compile the .c and .s file on macOS and test from the
mid-function outlining as well as the epilogue outlining.
For prologue outlining, what I'm most interested in is not unwinding from the
OUTLINED_FUNCTION there - it's how to handle unwinding from the original source
function that has no prologue. That's a trickier one to say "ignore any unwind
instructions, do a simple stack walk" because we don't have a distinct function
name, we need to detect the func call to the OUTLINED_FUNCTION at the beginning
of the instructions.
https://github.com/llvm/llvm-project/pull/204500
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
