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.

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

Implicit ParseFunctionRanges is not thread-safe #360

Closed
wrwilliams opened this issue Apr 4, 2017 · 1 comment
Closed

Implicit ParseFunctionRanges is not thread-safe #360

wrwilliams opened this issue Apr 4, 2017 · 1 comment
Assignees
@wrwilliams
Labels
bug
Projects
Dyninst analysis thread safety
Milestone
Release 10.0.0

Comments

@wrwilliams
Copy link
Member

As per subject, reported by @mwkrentel. Called inside the various methods to get inlines; add scoped locks around the construct-and-check.
@wrwilliams wrwilliams modified the milestone: STTO11-19 Apr 4, 2017
@wrwilliams wrwilliams self-assigned this Apr 4, 2017
@wrwilliams wrwilliams changed the title Implicit ParseFunctionRanges is not reentrant Implicit ParseFunctionRanges is not thread-safe Apr 4, 2017
@wrwilliams wrwilliams modified the milestones: STTO11-19, STTO11-18 Apr 4, 2017
@wrwilliams wrwilliams added the bug label Apr 5, 2017
@wrwilliams wrwilliams modified the milestones: STTO11-18, Release 10.0.0 Apr 10, 2018
@mxz297
Copy link
Member

mxz297 commented Nov 27, 2018

This is part of the larger issue of parallel dwarf parsing. #327

@mxz297 mxz297 closed this as completed Nov 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wrwilliams wrwilliams

Labels
bug
Projects
No open projects
Dyninst analysis thread safety
Unassigned
Milestone
Release 10.0.0
Development

No branches or pull requests
2 participants
@mxz297 @wrwilliams