fix: in TraceRefs it will return fatal error

Signed-off-by: yihong0618 <zouzou0208@gmail.com>

Author: yihong0618

Lib/test/test_repl.py

@@ -120,9 +120,12 @@ def test_exec_set_nomemory_hang(self):
             p.stdin.write(user_input)
         output = kill_python(p)
 
-        self.assertIn(p.returncode, (0, 1, 120))
+        # it can exit with MemoryError or Fatal Python error when --with-trace-refs
+        # it return -6 here
+        self.assertIn(p.returncode, (0, 1, 120, -6))
         self.assertGreater(len(output), 0)  # At minimum, should not hang
-        self.assertIn("MemoryError", output)
+        # Can result in either MemoryError exception or fatal error
+        self.assertTrue("MemoryError" in output or "Fatal Python error" in output)
 
     @cpython_only
     def test_multiline_string_parsing(self):

Python/ceval.c

@@ -912,13 +912,6 @@ _PyEval_EvalFrameDefault(PyThreadState *tstate, _PyInterpreterFrame *frame, int
                 int frame_lasti = _PyInterpreterFrame_LASTI(frame);
                 PyObject *lasti = PyLong_FromLong(frame_lasti);
                 if (lasti == NULL) {
-                    // gh-134163: If we can't allocate memory for lasti during exception handling,
-                    // this likely means we're in a severe memory shortage situation.
-                    if (!_PyErr_Occurred(tstate)) {
-                        // PyLong_FromLong should have set an exception
-                        // like _testcapi.set_nomemory(0), it might not. Ensure one is set.
-                        PyErr_NoMemory();
-                    }
                     // Instead of going back to exception_unwind (which would cause
                     // infinite recursion), directly exit to let the original exception
                     // propagate up and hopefully be handled at a higher level.