Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Analysis loop potentially caused by indirect branch/caller analysis #6314

Open
xusheng6 opened this issue Jan 14, 2025 · 1 comment
Open
Labels
Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Bug Issue is a non-crashing bug with repro steps

Comments

@xusheng6
Copy link
Member

xusheng6 commented Jan 14, 2025

We get an analysis loop when we open the attached database.

One of the function that is contributing to the infinite loop is 0x100a2db3. And I see the stack trace that leads to this function being marked as updates required involves indirect branch analysis

I feel like this is related to, or the same as #6222

@xusheng6 xusheng6 added Type: Bug Issue is a non-crashing bug with repro steps Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround labels Jan 14, 2025
@xusheng6
Copy link
Member Author

V35 folks should search for silent river galaxy fresh stone to find the relevant database

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Core Issue needs changes to the core Effort: Medium Issue should take < 1 month Impact: Medium Issue is impactful with a bad, or no, workaround Type: Bug Issue is a non-crashing bug with repro steps
Projects
None yet
Development

No branches or pull requests

1 participant