Attaching debugger to a running processes behave different in several cases

When attaching the debugger to a running process I noticed different behaviours when using MinGW/GDB configured projects or MSVC/CDB configured projects as well there are differents whether you compile some breakpoints into the application or not.

MSVC/CDB project:

• compiled without breakpoints set:
  Attaching works, but setting breakpoint(s) cannot be done. (always throws an exception and if you hit the breakpoint the debugger doesn't stop)

• compiled with breakpoints set:
  Attaching works and setting breakpoints behaves as mentioned before, except when you hit a compiled breakpoint. If so, all breakpoints (that threw an exception) are now known to the debugger and can be used normally and the compiled worked anyway. Further setting breakpoints works without throwing exceptions.

MinGW/GDB:

• compiled with and without breakpoints set:
  Attaching seems to work (it never uses GDB; instead it always starts the CDB for debugging) but it fails to load some symbol modules. Setting breakpoints throws always an exception. Hitting these or compiled breakpoints do not make the debugger stop.

Additional information:

• AttachRunningMinGW_WithoutCompiledBP
  • line 147 (Exception caused by setting breakpoint)

• AttachRunningMinGW_WithCompiledBP
  • line 165 (Exception caused by setting breakpoint)

• AttachRunningMSVC_WithoutCompiledBP
  • line 148 (Exception caused by setting breakpoint)

• AttachRunningMSVC_WithCompiledBP
  • line 154 (Exception caused by setting breakpoint - before hitting a compiled one, lines 155ff hitting a compiled breakpoint, line 195 hitting the breakpoint set threw the exception in line 154)