gh-104736: Fix test_gdb tests on ppc64le with clang

vstinner · vstinner · commit 2ea0fd836beb · 2023-09-13T05:52:25.000+02:00
Skip test_gdb tests on ppc64le if "bt" command returns on these
patterns:

* "Backtrace stopped: frame did not save the PC"
* " ?? ()"

gdb logs these messages when it fails to retrieve the backtrace when
Python is built with "clang -Og" on Linux ppc64le, especially with
LLVM clang 16. For example, on Fedora 38.
diff --git a/Lib/test/test_gdb.py b/Lib/test/test_gdb.py
@@ -246,6 +246,14 @@ def get_stack_trace(self, source=None, script=None,
             # gh-91960: On Python built with "clang -Og", gdb gets
             # "frame=<optimized out>" for _PyEval_EvalFrameDefault() parameter
             '(unable to read python frame information)',
+            # gh-104736: On Python built with "clang -Og" on ppc64le,
+            # "py-bt" displays a truncated or not traceback, but "where"
+            # logs this error message:
+            'Backtrace stopped: frame did not save the PC',
+            # gh-104736: When "bt" command displays something like:
+            # "#1  0x0000000000000000 in ?? ()", the traceback is likely
+            # truncated or wrong.
+            ' ?? ()',
         ):
             if pattern in out:
                 raise unittest.SkipTest(f"{pattern!r} found in gdb output")
