Commit b2fa6f41 authored by Russ Cox's avatar Russ Cox

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
parent 02903f83
...@@ -30,11 +30,13 @@ runtime·sighandler(ExceptionRecord *info, Context *r, G *gp) ...@@ -30,11 +30,13 @@ runtime·sighandler(ExceptionRecord *info, Context *r, G *gp)
bool crash; bool crash;
uintptr *sp; uintptr *sp;
/*
switch(info->ExceptionCode) { switch(info->ExceptionCode) {
case EXCEPTION_BREAKPOINT: case EXCEPTION_BREAKPOINT:
r->Eip--; // because 8l generates 2 bytes for INT3 r->Eip--; // because 8l generates 2 bytes for INT3
return 1; return 1;
} }
*/
if(gp != nil && runtime·issigpanic(info->ExceptionCode)) { if(gp != nil && runtime·issigpanic(info->ExceptionCode)) {
// Make it look like a call to the signal func. // Make it look like a call to the signal func.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment