I wish this help you Breakpoints are not used by compiler to produce debug information (pdb) or any other binaries. It's an options related to the Visual Studio solution. Visual Studio stores breakpoints in "SolutionName".suo file. This file is also used for other Solution User Options. If your projects are in different solutions it's not possible to automatically use the breakpoints from one in the other.
hop of those help? Rekaszeru's answer to this question shows how to set up Eclipse in order to always launch the previously launched application. You simply have to go to preferences / run-debug / launching and check the "Always launch previously launched application" box as he shown in the picture he used to illustrate his answer:
Customizing Project File to compile project and zip entire debug folder in msBuild
this will help You might be able to put a Debugger.Launch() statement in place of a breakpoint. I have had to use this many times when debugging applications that I don't control the application start and need more of a remote debugging scenario. The Debugger.Launch() will allow you to attach a new or existing VS instance to a running application. By doing that in your scenario, you can start to inspect the threads (both in your current VS, and any new VS you attach with the Debugger.Launch() to ensure that they are both aware of the same threads. Your original VS may be losing access to the threads that your callback are on and thereby is unable to break.
How to debug a project in Intellij while setting the breakpoints in another project
To fix this issue When working with multiple maven projects, I find it convenient to put both under a parent maven project. The two child projects are not aware of the parent and remain independent of each other, but by aggregating them on one parent pom, you can conveniently build and test them at the same time, keeping the dependent in sync with its dependency. When you do that, you can also create Run configurations for each project, launch them in debug mode, and put breakpoints in either or both of them. The parent pom stays in the parent folder of both projects, and does not need to go into source control because the child poms don't refer to it as their parent--its only for your convenience in working on both at the same time. Such a pom might look like: