From ff3f6bc722a18ea86452e16984d34bc021c87105 Mon Sep 17 00:00:00 2001
From: John Cortell <john.cortell@freescale.com>
Date: Fri, 30 Apr 2010 21:06:54 +0000
Subject: [PATCH] Updated comment to reflect the current status given a fix
 earlier today.

---
 .../utils/org/eclipse/cdt/utils/spawner/Spawner.java       | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/core/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/spawner/Spawner.java b/core/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/spawner/Spawner.java
index 41abe03670f..4bacde2ea36 100644
--- a/core/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/spawner/Spawner.java
+++ b/core/org.eclipse.cdt.core/utils/org/eclipse/cdt/utils/spawner/Spawner.java
@@ -41,10 +41,9 @@ public class Spawner extends Process {
 	 *    the 'kill' utility isn't available, send the process a CTRL-C
 	 *    <li>If the process is <i>not</i> a cygwin program, send the process a CTRL-C
 	 *    </ul>
-	 * <li>If the process this is being raised against was <i>not</i> launched by us, search for a console
-	 * window whose PID matches the one we're trying to raise a signal on. If we find one, then send keyboard
-	 * events to simulate the user hitting CTRL-C at that console. We do all this because we can't programatically
-	 * send a CTRL-C to a process that doesn't share our console.
+	 * <li>If the process this is being raised against was <i>not</i> launched by us, use 
+	 * DebugBreakProcess to interrupt it (sending a CTRL-C is easy only if we share a console 
+	 * with the target process) 
 	 * </ul>
 	 * 
 	 * On non-Windows, raising this just raises a POSIX SIGINT