From b2fa6f41a48b141e7307f9640f4ceb748a42b4cd Mon Sep 17 00:00:00 2001
From: Russ Cox <rsc@golang.org>
Date: Fri, 7 Mar 2014 14:22:17 -0500
Subject: [PATCH] runtime: comment out breakpoint in windows/386 sighandler

This code being buggy is the only explanation I can come up
with for issue 7325. It's probably not, but the only alternative
is a Windows kernel bug. Comment this out to see what breaks
or gets fixed.

Update #7325

LGTM=bradfitz
R=golang-codereviews, bradfitz
CC=golang-codereviews
https://golang.org/cl/72590044
---
 src/pkg/runtime/os_windows_386.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/pkg/runtime/os_windows_386.c b/src/pkg/runtime/os_windows_386.c
index 5048f51d61b..f6b54316948 100644
--- a/src/pkg/runtime/os_windows_386.c
+++ b/src/pkg/runtime/os_windows_386.c
@@ -30,11 +30,13 @@ runtime·sighandler(ExceptionRecord *info, Context *r, G *gp)
 	bool crash;
 	uintptr *sp;
 
+	/*
 	switch(info->ExceptionCode) {
 	case EXCEPTION_BREAKPOINT:
 		r->Eip--;	// because 8l generates 2 bytes for INT3
 		return 1;
 	}
+	*/
 
 	if(gp != nil && runtime·issigpanic(info->ExceptionCode)) {
 		// Make it look like a call to the signal func.