I have come across with some issues regarding BridgePoint’s thread handling. I start 3 threads from Java code. Sometimes not all the threads are started, however in the Java code they should start from one after another. If I restart several times the Verifier, then it works. (It is not the business logic in the Java code that prevents the thread from running.)
I have experienced, that BridgePoint allows at most 3 Java threads to run in my code. If I want to start more than 3 threads, BridgePoint kills the latter ones.
Another issue regarding threading: if 3 threads run simultaneously, BridgePoint terminates one after a while.
Do you have any idea, why BridgePoint is so strict with running Java threads?
Once you have it built you can use the you can run the Debug Launch Configuration “Eclipse Application > BP Application”. Then you can use the JDT debugger to set breakpoints, see the stack, watch variables, look at threads, etc…
Verifier is implemented in the org.xtuml.bp.debug.ui plug-in. I suggest you start by looking around in there.