mirror of
https://github.com/eclipse-cdt/cdt
synced 2025-04-29 19:45:01 +02:00
Bug 344890: Once we support starting a new process on a remote target, we should not use -exec-continue for that case, we must use -exec-run
This commit is contained in:
parent
93b8e52303
commit
d1cb95f6ed
1 changed files with 5 additions and 3 deletions
|
@ -439,13 +439,15 @@ public class StartOrRestartProcessSequence_7_0 extends ReflectionSequence {
|
|||
* This method can be overridden to allow for customization.
|
||||
*/
|
||||
protected boolean useContinueCommand() {
|
||||
// When doing remote debugging, we use -exec-continue instead of -exec-run
|
||||
// Restart does not apply to remote sessions
|
||||
// Note that restart does not apply to remote sessions
|
||||
IGDBBackend backend = fTracker.getService(IGDBBackend.class);
|
||||
if (backend == null) {
|
||||
return false;
|
||||
}
|
||||
return backend.getSessionType() == SessionType.REMOTE;
|
||||
// When doing remote non-attach debugging, we use -exec-continue instead of -exec-run
|
||||
// For remote attach, if we get here it is that we are starting a new process
|
||||
// (multi-process), so we want to use -exec-run
|
||||
return backend.getSessionType() == SessionType.REMOTE && !backend.getIsAttachSession();
|
||||
}
|
||||
|
||||
}
|
Loading…
Add table
Reference in a new issue