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 5048f51d61b51fceb867b7c3fb038a3ddbd437fe..f6b54316948e601c3358de3f7a86a62b64ee75da 100644 (file)
--- 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.