Handling multiple breakpoints in Trap Redux

In a previous post I worked on getting Trap building on a new system and found that the unit tests were not passing. It looked like I had found a real bug: I found: The first call to breakpoint_resolve must be when the breakpoint in main is reached. And the second call is 3 bytes later. I think this is trying to resolve the stop in execution that happens when we are in state…