Now I encounter another tricky problem with GDB debugger on my Win64 system.
The Debugger can not terminate normally. After I press the Stop Debugger Button, the debug output window will output similar lines like
Trying to interrupt process with pid: 5368; child pid: 5368 gdb pid: 13964, but the debugger is still in running, even if one minute later,
the Stop Debugger button is still in RED! Please refer to the attachment, you would find out the bizarre behaviour.
This is not the first time I encounter this phenomenon, actually I reinstall the Code::Blocks 17.12 for many times, the problem still exists.
It's very clumbsy to terminate the GDB debugger in the Task Manager Window or rebuild the project and only at this moment,
the Code::Blocks will force to stop the GDB debugger.
I begin to doubt about if C::B doesn't support to work normally with GDB debugger on Win64, and CDB may be a better choice on my computer.
Anyone can explain the phenomenon?