From: Russ Cox <rsc@golang.org>
Date: Fri, 7 Mar 2014 19:22:17 +0000 (-0500)
Subject: runtime: comment out breakpoint in windows/386 sighandler
X-Git-Tag: go1.3beta1~423
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=b2fa6f41a48b141e7307f9640f4ceb748a42b4cd;p=gostls13.git

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
---

diff --git a/src/pkg/runtime/os_windows_386.c b/src/pkg/runtime/os_windows_386.c
index 5048f51d61..f6b5431694 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.