Bug 525692 - GDB Hardware Debugging: run command execution deferred
Summary: GDB Hardware Debugging: run command execution deferred
Status: RESOLVED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 9.3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 9.4.0   Edit
Assignee: John Dallaway CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-06 12:56 EDT by John Dallaway CLA
Modified: 2017-10-11 16:18 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Dallaway CLA 2017-10-06 12:56:41 EDT 
When using a GDB Hardware Debugging launch with the "Resume" option enabled on the Startup page, any run commands specified by the user are issued _after_ execution has been resumed. These run commands are therefore not processed by GDB until the target is next suspended.

Execution of run commands should occur _before_ execution is resumed within the launch sequence. The layout of user interface elements within the Startup page should be modified to reflect the revised launch sequence.

Fix to follow.
Comment 1 Eclipse Genie CLA 2017-10-08 07:43:03 EDT 
New Gerrit change created: https://git.eclipse.org/r/106424