You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
No matter which trace is loaded with the method
loadEventTrace
from theTraceProcessor
class, the fieldhandlerEvents
will always be empty. This is caused by a bug with the iterators (fast and slow) used in methodparseMessageHandlers
which makes it behave in such a way that the variablese
andnextEvent
move like this:The text was updated successfully, but these errors were encountered: