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

Jump to bottom

ValueHandle is easy to confuse with active CallbackVHs #5532

Closed
llvmbot opened this issue Oct 10, 2009 · 1 comment
Closed

ValueHandle is easy to confuse with active CallbackVHs #5532

llvmbot opened this issue Oct 10, 2009 · 1 comment
Labels
bugzilla Issues migrated from bugzilla llvm:core

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Oct 10, 2009

Bugzilla Link 5160
Resolution FIXED
Resolved on Oct 12, 2009 12:46
Version trunk
OS All
Attachments Some tests for the brokenness, Proposed fix
Reporter LLVM Bugzilla Contributor

Extended Description

When CallbackVHs modify ValueHandles that refer to the same Value, this can crash the program or cause AssertingVHs to fail when they actually no longer refer to the Value. I'll be working on a fix.
@llvmbot
Copy link
Collaborator Author

llvmbot commented Oct 12, 2009

Committed as r83861.

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
augusto2112 pushed a commit to augusto2112/llvm-project that referenced this issue Nov 3, 2022
@shahmishal
Merge pull request llvm#5532 from akyrtzi/pr/stable/remove-remote-con…
bfb3b8b 
…nection-timeout

[stable/20220421][RemoteCachingService] Remove the initial connection timeout
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla llvm:core
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@llvmbot