From 7a3eddc19f70b6965077eae7746fb6b509bf1cdd Mon Sep 17 00:00:00 2001 From: Med Ismail Bennani Date: Thu, 18 Dec 2025 23:22:53 +0100 Subject: [PATCH] [lldb/test] Fix failure caused by leading zero in TestScriptedFrameProvider.py This should fix a test failure in TestScriptedFrameProvider.py: https://lab.llvm.org/buildbot/#/builders/18/builds/23398/steps/6/logs/stdio This is a happening because on 32bit system, addresses don't have the leading zeroes. This patch removes them to satisfy the checks. Signed-off-by: Med Ismail Bennani --- .../TestScriptedFrameProvider.py | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/lldb/test/API/functionalities/scripted_frame_provider/TestScriptedFrameProvider.py b/lldb/test/API/functionalities/scripted_frame_provider/TestScriptedFrameProvider.py index e2b0f0f9cd50..0a5b9d9b8395 100644 --- a/lldb/test/API/functionalities/scripted_frame_provider/TestScriptedFrameProvider.py +++ b/lldb/test/API/functionalities/scripted_frame_provider/TestScriptedFrameProvider.py @@ -624,15 +624,15 @@ class ScriptedFrameProviderTestCase(TestBase): self.assertIn("unknown_function_2", output) # Should show PC addresses in hex format. - self.assertIn("0x0000000001234000", output) - self.assertIn("0x0000000005678000", output) + self.assertIn("1234000", output) + self.assertIn("5678000", output) # Verify PC and function name are properly separated by space. - self.assertIn("0x0000000001234000 unknown_function_1", output) - self.assertIn("0x0000000005678000 unknown_function_2", output) + self.assertIn("1234000 unknown_function_1", output) + self.assertIn("5678000 unknown_function_2", output) # Should NOT show invalid address. - self.assertNotIn("0xffffffffffffffff", output.lower()) + self.assertNotIn("ffffff", output.lower()) # Verify frame 2 is the original real frame 0. frame2 = thread.GetFrameAtIndex(2)