handlerEvents field in TraceProcessor never populated
jcp19 opened this issue · 0 comments
jcp19 commented
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