shylie/llvm-project
1
0
Fork 0
Code Issues Pull Requests Actions 6 Packages Projects Releases Wiki Activity

[lldb/test] Fix failure caused by leading zero in TestScriptedFrameProvider.py

Browse Source 
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 <ismail@bennani.ma>
This commit is contained in:
Med Ismail Bennani 2025-12-18 23:22:53 +01:00
parent c9aea6248a
commit 7a3eddc19f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
lldb/test/API/functionalities/scripted_frame_provider/TestScriptedFrameProvider.py
View File

@ -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)