Community
Participate
Working Groups
Build Identifier: 20100917-0705 In debug perspective, when you restart the debugged application an error window message appears: Target request failed: The "remote" target does not support "run". Try "help target" or "continue". It should be possible to change the predefined "run" command to something customizable (i.e. monitor commands) so that restart is possible without relaunching the debug session. Reproducible: Always Steps to Reproduce: 1.Setup a GDB Hardware Debug session with remote gdbserver. 2.Launch the debug session. 3.Right-click on the debugged application that is listed in the "Debug" window and select "Restart".
With current version (8.3.0.201402142303), the message does not show up in an error window, but is only visible in the 'gdb traces', leading the user to the assumption restart worked. GDB Hardware Debugging sessions are 'remote' targets, but the launch configuration does not set "org.eclipse.cdt.launch.DEBUGGER_START_MODE" to "remote". On the other hand, this would disable the complete 'restart'. Better solution would be to have a sequence for the restart behavior.
*** Bug 257357 has been marked as a duplicate of this bug. ***
In the general case, restarting a "GDB Hardware Debugging" debug session without a full relaunch is not possible. The complete launch sequence may be required to restore correct target state. The "Restart" action should be disabled for "GDB Hardware Debugging" launches as it is for "C/C++ Remote Application" launches.
New Gerrit change created: https://git.eclipse.org/r/110445
Gerrit change https://git.eclipse.org/r/110445 was merged to [master]. Commit: http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=a80f50a7259485586097ba1d987feefde1643d9c