multi threading program analyze with eclipse debugger

I demonstrated the danger of sharing variables among multiple threads without correct synchronization, and why multi-threading bug is called heisonbug -- they are non-observable -- they results depend on machine states, when you try to observe it, you are not running the program in the same machine state, you observed a different result.

In this video, we will play the role of jvm, step through the threads execution one step at a time. Still we can not observe the heisonbug. The take away is: get the program correct at the first place is much more easier than trying to understand what's going wrong later.

[logicbuffer]

This was helpful, thanks for the insights.