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

Add unknown thread ID #392

Closed
sim642 opened this issue Oct 13, 2021 · 2 comments · Fixed by #1224
Closed

Add unknown thread ID #392

sim642 opened this issue Oct 13, 2021 · 2 comments · Fixed by #1224
Assignees
@karoliineh
Labels
cleanup Refactoring, clean-up good first issue
Milestone
v2.4.0

Comments

@sim642
Copy link
Member

sim642 commented Oct 13, 2021

As revealed in #388, it would be very good to have an unknown thread ID, just like the unknown address in address sets. This would allow keeping known thread IDs while invalidating/joining with incompatible/etc.
@sim642 sim642 added the cleanup Refactoring, clean-up label Oct 13, 2021
@karoliineh karoliineh self-assigned this Oct 26, 2023
@karoliineh karoliineh mentioned this issue Oct 27, 2023
Merged
@michael-schwarz
Copy link
Member

Anything left to be done here now that #1224 is merged?

@sim642 sim642 linked a pull request Jan 29, 2024 that will close this issue
Add unknown thread ID #1224
Merged
@sim642 sim642 added this to the v2.4.0 milestone Jan 29, 2024
@sim642
Copy link
Member Author

sim642 commented Jan 29, 2024

I don't think so. Looks like the issue just wasn't fully linked with the PR.

@sim642 sim642 closed this as completed Jan 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karoliineh karoliineh

Labels
cleanup Refactoring, clean-up good first issue
Projects
None yet
Milestone
v2.4.0
Development

Successfully merging a pull request may close this issue.

Add unknown thread ID goblint/analyzer
3 participants
@sim642 @michael-schwarz @karoliineh