Bizarre debugging behavior - VS2008

[xlar54]

Hello,

I have a case where I am debugging application A, which is a client to
a server application. To test some functionality, I run another
instance of application A. I am seeing in some cases that the
debugger actually stops at breakpoints, in the *wrong* instance - the
one I did NOT run from within the debugger. How is this possible? Is
this a debugger...bug?

Thanks

[Jeroen Mostert]

xlar54 wrote:

I have a case where I am debugging application A, which is a client to
a server application. To test some functionality, I run another
instance of application A. I am seeing in some cases that the
debugger actually stops at breakpoints, in the *wrong* instance - the
one I did NOT run from within the debugger.

How do you know? In other words, what convinces you this isn't a user error?
If you choose Debug -Stop Debugging, does the process you expect terminate?

How is this possible? Is this a debugger...bug?

It would be the first time I see it. Which doesn't say anything, of course.

If you want to confirm this is a Visual Studio problem, you could run it
under a different debugger, like mdbg (installed with the Windows SDK) or
WinDbg (this has a bit of a learning curve, especially if you want to do
unmanaged debugging with it).

--
J.