Accept the 32-bit allocation-overflow rejection in the frame-count test

On 32-bit builds a footer frame count of 0xFFFFFFFF overflows the
allocation size, so the size_t overflow guard raises OverflowError before
the count-vs-file-size guard raises ValueError.  Accept either rejection.

Author: tonghuaroot

Lib/test/test_profiling/test_sampling_profiler/test_binary_format.py

@@ -1090,14 +1090,19 @@ def test_open_rejects_frame_count_larger_than_file(self):
         max_frames = (size - frame_off) // self.MIN_FRAME_ENTRY_SIZE
         self._patch_footer_count(filename, self.FTR_OFF_FRAMES, 0xFFFFFFFF)
 
-        with self.assertRaises(ValueError) as cm:
+        # 0xFFFFFFFF frames exceed the file on every platform.  On a 32-bit
+        # build it also overflows the allocation size, so the size_t overflow
+        # guard (OverflowError) fires before the count-vs-file-size guard
+        # (ValueError); either rejection is correct.
+        with self.assertRaises((ValueError, OverflowError)) as cm:
             with BinaryReader(filename):
                 pass
-        self.assertEqual(
-            str(cm.exception),
-            f"Invalid frame count 4294967295 exceeds maximum "
-            f"possible {max_frames}",
-        )
+        if isinstance(cm.exception, ValueError):
+            self.assertEqual(
+                str(cm.exception),
+                f"Invalid frame count 4294967295 exceeds maximum "
+                f"possible {max_frames}",
+            )
 
     def test_open_accepts_frame_count_at_capacity_boundary(self):
         """A frame count at the file-size cap opens; one more is rejected."""