8000 Valgrind frontend sometimes misses new threads · Issue #2 · VANDAL/prism · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Valgrind frontend sometimes misses new threads #2

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
Open
mikelui opened this issue Jun 15, 2018 · 0 comments
Open

Valgrind frontend sometimes misses new threads #2

mikelui opened this issue Jun 15, 2018 · 0 comments
Labels
bug Something isn't working frontend/valgrind

Comments

@mikelui
6BD2 Copy link
Member
mikelui commented Jun 15, 2018

Sigrind, the modified Callgrind tool, uses Callgrind's implementation of differentiating threads which can sometimes miss new threads.

This is because Callgrind uses Valgrind's internal thread id's, which reuses id's of exited threads.

So the following can happen:

Created - tid 1
Created - tid 2
Created - tid 3
Created - tid 4
Exited  - tid 2
Created - tid 2 <-- **Reusing old thread id** should be unique tid 5!

Prism will then conflate events from unique tid 2 and unique tid 5, treating them as coming from the same thread.
@mikelui mikelui added bug Something isn't working frontend/valgrind labels Jun 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working frontend/valgrind
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mikelui
0