fntneves / falcon Goto Github PK

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

At times, I need to have two separate instances of TraceProcessor in order to handle two different traces in the same program. However, this class is implemented as a singleton. Is there any particular reason for this class to be be implemented like this?

At first sight, it looks like the only change required to make this class 'not a singleton' would be to change the access modifier on the only available constrcutor.