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

handlerEvents field in TraceProcessor never populated #43

Closed
jcp19 opened this issue Jan 17, 2020 · 0 comments
Closed

handlerEvents field in TraceProcessor never populated #43

jcp19 opened this issue Jan 17, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@jcp19
Copy link
Collaborator

jcp19 commented Jan 17, 2020

No matter which trace is loaded with the method loadEventTrace from the TraceProcessor class, the field handlerEvents will always be empty. This is caused by a bug with the iterators (fast and slow) used in method parseMessageHandlers which makes it behave in such a way that the variables e and nextEventmove like this:

trace in thread t: WRITE_x ; RCV_m; HANDLERBEGIN_m; READ_x; ...

1st iteration:
value of e: WRITE_x
value of nextEvent: RCV_m

2nd iteration:
value of e: HANDLERBEGIN_m
value of nextEvent: READ_x
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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fntneves @jcp19