Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361881

Summary: GDB Hardware Debugging options "Reset and Delay" and "Halt" in Startup tab have no effect on remote target
Product: [Tools] CDT Reporter: Artem Pisarenko <artymen>
Component: cdt-debugAssignee: John Dallaway <john>
Status: RESOLVED FIXED QA Contact: Ken Ryall <ken.ryall>
Severity: minor    
Priority: P3 CC: cdtdoug, john, jonah, lucdono, pawel.1.piech
Version: 8.0   
Target Milestone: 9.4.0   
Hardware: PC   
OS: Windows XP   
See Also: https://git.eclipse.org/r/110885
https://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=ebbe75d37f5b39a2815f82d07a08ea0602582451
Whiteboard:
Attachments:
Description Flags
Reset command not defined for Generic TCP/IP device none

Description Artem Pisarenko CLA 2011-10-25 01:01:59 EDT 
Build Identifier: 20100617-1415

GDB Hardware Debugging launch configuration have options "Reset and Delay" and "Halt" on Startup tab. They have no effect for remote target debugging on Generic TCP/IP JTAG Device. (I didn't tried for non-remote because I don't understand how jtag debugging may be non-remote. Jtag-only meaning comes from name org.eclipse.cdt.debug.gdbjtag.feature.group.) During launch CDT don't implement any reset command to GDB server.
I think it should be implemented or removed at all because it confuses. I didn't used "monitor reset" initialization command because thought CDT did it itself and I lost a lot of time trying to understand why target debugging acts inappropriately.

Reproducible: Always
Comment 1 John Dallaway CLA 2017-11-01 17:02:33 EDT 
At minimum, the GDB Hardware Debugging launch configuration should report when a requested launch command is not defined rather than ignoring the request.
Comment 2 Eclipse Genie CLA 2017-11-01 17:38:28 EDT 
New Gerrit change created: https://git.eclipse.org/r/110885
Comment 5 Luca D\'Onofrio CLA 2018-02-01 11:10:29 EST 
Hi All,
as far as I see from the code, the implementation of the GenericDevice always sets an error if the command list is empty.
IMHO a warning should be enough, without stopping the debug session to work at all.
If you use a Generic TCP/IP device (i.e. connecting to an external server), you will not be able to debug at all. (please see the attached screenshot).

Please let me know your comments.

Regards,
L
Comment 6 Luca D\'Onofrio CLA 2018-02-01 11:11:05 EST 
Created attachment 272505 [details]
Reset command not defined for Generic TCP/IP device
Comment 7 John Dallaway CLA 2018-02-01 12:29:18 EST 
Luca, the behaviour (described by the originator of this ticket) where a user enables "Reset and Delay" or "Halt" within the user interface but these selections are ignored on launch can be highly confusing.

Ideally, these user interface elements would be disabled where not supported by the selected JTAG device, but usability issues arise when it is not obvious why a user interface element is disabled and how it may be enabled. At present, JTAG device selection is on a different page of the launch configuration dialog. Also, the existing software architecture does not readily allow support for the "Reset and Delay" or "Halt" commands to be determined prior to launch.

The current implementation does make it clear that the user will not get what has been requested. It is still possible to debug using the "Generic TCP/IP" JTAG device simply by ensuring that both "Reset and Delay" and "Halt" boxes are unchecked. These are the default settings.
Comment 8 Luca D\'Onofrio CLA 2018-02-01 12:57:23 EST 
Hi John,
thanks for your reply. Understood.

Regards,
Luca
Comment 9 Jonah Graham CLA 2018-02-01 15:22:54 EST 
If you have seen over the "Reset Command not defined for device 'Generic TCP/IP'" then See Bug 529171 Comment 9 as there is a plan to change the defaults so that this error does not occur.