[Event cannot happen] printing conflicting event number in the executable trace

[Schmill]

When using the verifier, I get a well formatted message indicating the event that cannot happen in the current state. but when observing the trace oof the generated executable, I can only see the state number.

I tried to modify the dispatch function by adding printf( "Event: %s \n", GetOoaEventNumber( event )); but unfortunately this yields null.

How can I trace the conflicting event Number?

Thank you.

[cort]

Did you mark the state transition tracing on? (.invoke MarkStateTransitionTracingOn( “*” ))
This mark is found in the domain.mark file.

[Schmill]

Indeed this mark is enabled. but I do not get the event number, here is a sample trace:
Event cannot happen: ND current_state = 3

[cort]

Hmm, that looks like it should work.

[Schmill]

I used the UserEventCantHappenCalloutf now with the line printf( "Event: %hhu in state: %hhu \n", event_number,current_state);
prints:
Event: 0 in state: 3
Also cheeked in another place with different Cannot Happen, it is also 0.

[Schmill]

It appears that I was confused by the fact that event_number does not correspond to the event numbers displayed in Bridgepoint, so 0 is a valid number.

[cort]

Right, there is a mapping. Because BridgePoint allows event numbers to be anything. And the dispatcher needs to index into an array.

[Author]

Posts