Skip to content

Conversation

@rlavaee
Copy link
Contributor

@rlavaee rlavaee commented Nov 11, 2025

No description provided.

@llvmbot llvmbot added the lldb label Nov 11, 2025
@rlavaee rlavaee changed the title Fix lld failure caused by 95db31e7f6. [LLDB] Fix lldb failure caused by 95db31e7f6. Nov 11, 2025
@llvmbot
Copy link
Member

llvmbot commented Nov 11, 2025

@llvm/pr-subscribers-lldb

Author: Rahman Lavaee (rlavaee)

Changes

Full diff: https://github.com/llvm/llvm-project/pull/167423.diff

1 Files Affected:

  • (modified) lldb/test/API/functionalities/thread/step_until/function.list (+3-1)
diff --git a/lldb/test/API/functionalities/thread/step_until/function.list b/lldb/test/API/functionalities/thread/step_until/function.list
index 5900fe8c35069..43c121eff9631 100644
--- a/lldb/test/API/functionalities/thread/step_until/function.list
+++ b/lldb/test/API/functionalities/thread/step_until/function.list
@@ -1 +1,3 @@
-!call_me
+v1
+f call_me
+c 0

@rlavaee rlavaee changed the title [LLDB] Fix lldb failure caused by 95db31e7f6. [LLDB] Fix lldb failure caused by @95db31e7f6. Nov 11, 2025
@rlavaee rlavaee changed the title [LLDB] Fix lldb failure caused by @95db31e7f6. [LLDB] Fix lldb failure caused by 95db31e7f6. Nov 11, 2025
@rlavaee rlavaee merged commit cd6c761 into llvm:main Nov 11, 2025
10 of 12 checks passed
DavidSpickett added a commit that referenced this pull request Nov 11, 2025
After #167359 / 95db31e.

A fix was attempted in #167423 but was not quite enough.

From what I could understand, in v1 format you have to specify
all the basic blocks. Where before !call_me implied they were all
cold (I think, very shaky understanding here).

For this test we want to see blocks like call_me/foo/call_me.
So adding a line for block 1 fixes the tests.

It could produce more blocks at some point but I think as long
as foo is within two of them, it'll be fine.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants