| Summary: | Restart not working in GDB Hardware Debugging | ||
|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Marco Vedovati <marco.v83> |
| Component: | cdt-debug | Assignee: | John Dallaway <john> |
| Status: | RESOLVED FIXED | QA Contact: | Ken Ryall <ken.ryall> |
| Severity: | normal | ||
| Priority: | P3 | CC: | cdtdoug, harm.verhagen, john, jon, pawel.1.piech, support_jlink |
| Version: | 8.0 | ||
| Target Milestone: | 9.4.0 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| See Also: |
https://git.eclipse.org/r/110445 https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=a80f50a7259485586097ba1d987feefde1643d9c |
||
| Whiteboard: | |||
|
Description
Marco Vedovati
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 |