'Breakpoints in Parallel Processes behave abnormally?
I am developing software for a legacy computer system that has several independent computer racks that are all in communication with each other. When building each of the executive processes on each machine in debug mode, I can independently set breakpoints in each of the processes' code. On a particular machine, the breakpoints often take multiple clicks of the "Next Instruction" button for the progress to increment to the next instruction, almost as if it is having to communicate to the other processes where it is in order to advance while stopped at a breakpoint.
Are there any special rules/circumstances that might explain behavior like this? What can happen if you are debugging a system with only one process that is built/ran in debug mode? Do all processes need to be in debug mode as opposed to in release mode to properly set breakpoints and debug the system?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|