Bug #17451 2010-08-21 02:46
pfong
Stop Debugger does not work on windows with remote target
When I press "Stop Debugger", it says "Trying to pause the running process..." in the Debugger window but nothing happens.
I am trying to debug an ARM target using GDB 7.1 connected through OpenOCD. However, the same problem happens with the MSP430 as well as described in this forum thread: http://forums.codeblocks.org/index.php/topic,12412.0.html
There is no problem with the same setup under Linux.
- Category
- Debugger
- Group
- Status
- Closed
- Close date
- 2012-11-10 19:17
- Assigned to
- tpetrov
History
Actually, you do not need an embedded target to see this problem. It happens with a remote PC target.
So, to reproduce the problem on Windows with the MinGW bundled with Code::Blocks with a new console program (AKA helloworld) created by the create project wizard:
1. Create a new console project. It must be in a path without spaces for GDB to work.
2. The project is automatically populated with a main that prints out "Hello world!". Add a "while (1)" in it so that it runs forever.
3. Build the debug version.
4. In code::blocks set the remote GDB target to 127.0.0.1 :2314
5. In a command prompt run: gdbserver :2314 helloworld.exe
6. Start the debugger in code::blocks. This should start the process. It will consume all your cpu in the while(1) loop.
7. Press the stop debugger button (X in red octagon). Code::blocks prints out "Trying to pause the running process..." in the Debugger output window but the process continues to run.
Have you tried the CB from debugger's branch?
There I've implemented this feature correctly.
Please test a recent debugger's branch nightly and report back if the problem is still there.
Report is closed.
Note: This is a preformatted standard message.
Possible reasons for closing this report are:
* the developer in charge of the issue
- could not reproduce it despite trying several times
- did not get sufficient information
- got no reply to an inquiry for specific information
* the report is quite a bit dated of now, and
- no user comments have been added for several weeks
- significant changes have been made to the code
- no other developer could reproduce it either
It is assumed that the problem does not persist and the report
can be closed.
If the problem reappears in future releases, please feel free to
re-open this report and provide precise information on how to
reproduce it.