Description
Note:
- Looks more like a known issue
- Works on 32bit Windows
This makes use of the Win32 API DebugBreakProcess() which reports back success. The Debugger reports:
[New Thread 3660.0x13b8]
>~"error return windows-nat.c:1279 was 299\n"
>*running,thread-id="all"
>=thread-exited,id="2",group-id="3660"
sThread 2 in group 3660 exited
Reproducible with the attached sample program, which can break applications only under CDB/not gdb. Ctrl-C in gdb works, though.
Resolution: Known issue ATM, DebugBreakProcess must have same 'bitness' as the application.