Skip to content

[Cherry-pick into next] [lldb] Acquire the map lock after deriving the lookup key #9641

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.

Sign up for GitHub

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
Merged
merged 1 commit into from
Nov 20, 2024
Merged

[Cherry-pick into next] [lldb] Acquire the map lock after deriving the lookup key #9641

merged 1 commit into from
Nov 20, 2024

Conversation

@adrian-prantl
Copy link

@adrian-prantl adrian-prantl commented Nov 20, 2024 

commit a657eef5a38d74d92c2204ebce00cddfe5413b90
Author: Adrian Prantl <aprantl@apple.com>
Date:   Tue Nov 19 15:50:15 2024 -0800

    [lldb] Acquire the map lock after deriving the lookup key
    
    The computation of the key may itself does DWARF lookups which may
    acquire additional locks through callbacks into TypeSystem.
    
    rdar://139841554

@adrian-prantl
[lldb] Acquire the map lock after deriving the lookup key
662aa3c 
The computation of the key may itself does DWARF lookups which may
acquire additional locks through callbacks into TypeSystem.

rdar://139841554
(cherry picked from commit a657eef)
@adrian-prantl adrian-prantl merged commit 8e9932c into swiftlang:next Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@JDevlieghere JDevlieghere Awaiting requested review from JDevlieghere JDevlieghere is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@adrian-prantl