Bug 560274 - Race condition when updating debug toolbar button statesY20200318-0540Y20200317-0225Y20200316-1300Y20200316-0820Y20200314-1405Y20200313-1100Y20200311-0915Y20200310-0525Y20200305-0600Y20200225-1040X20200306-0700X20200305-1900X20200305-0700X20200304-1900X20200304-0700X20200303-1900X20200303-0700X20200302-1900X20200302-0930X20200302-0700X20200301-1900X20200301-0700X20200229-1900X20200229-0700X20200228-1900X20200228-0700X20200228-0520X20200227-1900X20200227-0700X20200227-0130X20200226-0700X20200225-1900X20200225-0700X20200224-1900X20200224-0700S4_15_0_RC2S4_15_0_RC1R4_15I20200305-0155I20200304-1800I20200304-0600I20200303-1800I20200303-0600I20200302-1800I20200302-0600I20200301-2310I20200301-1800I20200301-0600I20200301-0030I20200229-1800I20200229-0600I20200228-1800I20200226-1800I20200226-0600I20200225-1800I20200225-0600I20200224-1800I20200224-0600

This change adjusts the scheduling rule when updating toolbar command
enablement via
"org.eclipse.debug.internal.core.commands.ForEachCommand", e.g. the
suspend toolbar enabled button state.

The new rule is exclusive per command, as opposed to exclusive per
selection type. I.e. before, debug target updates were exclusive, stack
frame updates were exclusive, etc. Now, disconnect command updates are
exclusive, suspend command updates are exclusive, etc.

Change-Id: Ia22232b0a55c3aba429bc980ec5a26eb238afd44
Signed-off-by: Simeon Andreev <simeon.danailov.andreev@gmail.com>

1 files changed, 28 insertions, 0 deletions

diff --git a/org.eclipse.debug.core/core/org/eclipse/debug/internal/core/commands/ForEachCommand.java b/org.eclipse.debug.core/core/org/eclipse/debug/internal/core/commands/ForEachCommand.java
index a1b418f4d..e222a72b5 100644
--- a/org.eclipse.debug.core/core/org/eclipse/debug/internal/core/commands/ForEachCommand.java
+++ b/org.eclipse.debug.core/core/org/eclipse/debug/internal/core/commands/ForEachCommand.java
@@ -15,8 +15,10 @@ package org.eclipse.debug.internal.core.commands;
 
 import org.eclipse.core.runtime.CoreException;
 import org.eclipse.core.runtime.IProgressMonitor;
+import org.eclipse.core.runtime.jobs.ISchedulingRule;
 import org.eclipse.debug.core.IRequest;
 import org.eclipse.debug.core.commands.AbstractDebugCommand;
+import org.eclipse.debug.core.commands.IDebugCommandRequest;
 import org.eclipse.debug.core.commands.IEnabledStateRequest;
 
 /**
@@ -26,6 +28,8 @@ import org.eclipse.debug.core.commands.IEnabledStateRequest;
  */
 public abstract class ForEachCommand extends AbstractDebugCommand {
 
+	private final ExclusiveRule exclusiveRule = new ExclusiveRule();
+
 	@Override
 	protected void doExecute(Object[] targets, IProgressMonitor monitor, IRequest request) throws CoreException {
 		for (Object target : targets) {
@@ -49,4 +53,28 @@ public abstract class ForEachCommand extends AbstractDebugCommand {
 
 	protected abstract boolean isExecutable(Object target);
 
+	/*
+	 * Do not allow parallel update requests for the same command, since those
+	 * can result in race conditions, where one selected element enables a
+	 * command and another selected element disables the command. Depending on
+	 * which request is processed first, the debug command could end up with the
+	 * wrong enabled state. See bug 560274.
+	 */
+	@Override
+	protected ISchedulingRule getEnabledStateSchedulingRule(IDebugCommandRequest request) {
+		return exclusiveRule;
+	}
+
+	static class ExclusiveRule implements ISchedulingRule {
+
+		@Override
+		public boolean contains(ISchedulingRule rule) {
+			return rule == this;
+		}
+
+		@Override
+		public boolean isConflicting(ISchedulingRule rule) {
+			return contains(rule);
+		}
+	}
 }