From c4c57e5c0eb79795d4fd1d9d8292455567c60070 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
 <31488909+miss-islington@users.noreply.github.com>
Date: Tue, 31 Aug 2021 08:53:17 -0700
Subject: bpo-45061: Enhance faulthandler traceback wit no Python frame
 (GH-28090)

Fix indentation of <no Python frame> message in a faulthandler
traceback or a Fatal Python error traceback. Example:

Current thread 0x00007f03896fb740 (most recent call first):
  Garbage-collecting
  <no Python frame>
(cherry picked from commit 888d4cc06b887e77f281ba4d640e281cb4c61b7b)

Co-authored-by: Victor Stinner <vstinner@python.org>
---
 Python/traceback.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Python/traceback.c b/Python/traceback.c
index 88ffc01..9b23f45 100644
--- a/Python/traceback.c
+++ b/Python/traceback.c
@@ -801,7 +801,7 @@ dump_traceback(int fd, PyThreadState *tstate, int write_header)
     // not modify Python objects.
     frame = tstate->frame;
     if (frame == NULL) {
-        PUTS(fd, "<no Python frame>\n");
+        PUTS(fd, "  <no Python frame>\n");
         return;
     }
 
-- 
cgit v0.12