aboutsummaryrefslogtreecommitdiff
path: root/src/pkg/runtime/linux
diff options
context:
space:
mode:
authorRuss Cox <rsc@golang.org>2011-02-23 15:42:13 -0500
committerRuss Cox <rsc@golang.org>2011-02-23 15:42:13 -0500
commit59ce067da8d9e7d968e51f31fb532ed2369f205a (patch)
treeb75d130f5edf0f96a23f68d7af8e131833f70d69 /src/pkg/runtime/linux
parente0a2c5d4b540934e06867710fe7137661a2a39ec (diff)
downloadgo-59ce067da8d9e7d968e51f31fb532ed2369f205a.tar.xz
runtime: omit breakpoint during terminal panic
A terminal panic (one that prints a stack trace and exits) has been calling runtime.breakpoint before calling exit, so that if running under a debugger, the debugger can take control. When not running under a debugger, though, this causes an additional SIGTRAP on Unix and pop-up dialogs on Windows. Support for debugging Go programs has gotten good enough that we can rely on the debugger to set its own breakpoint on runtime.exit if it wants to look around. R=r, r2 CC=golang-dev https://golang.org/cl/4222043
Diffstat (limited to 'src/pkg/runtime/linux')
-rw-r--r--src/pkg/runtime/linux/386/signal.c1
-rw-r--r--src/pkg/runtime/linux/amd64/signal.c1
2 files changed, 0 insertions, 2 deletions
diff --git a/src/pkg/runtime/linux/386/signal.c b/src/pkg/runtime/linux/386/signal.c
index 7f20d058b8..bd918c7ea5 100644
--- a/src/pkg/runtime/linux/386/signal.c
+++ b/src/pkg/runtime/linux/386/signal.c
@@ -100,7 +100,6 @@ runtime·sighandler(int32 sig, Siginfo *info, void *context, G *gp)
runtime·dumpregs(r);
}
- runtime·breakpoint();
runtime·exit(2);
}
diff --git a/src/pkg/runtime/linux/amd64/signal.c b/src/pkg/runtime/linux/amd64/signal.c
index 462f9a74d7..ea0932523e 100644
--- a/src/pkg/runtime/linux/amd64/signal.c
+++ b/src/pkg/runtime/linux/amd64/signal.c
@@ -110,7 +110,6 @@ runtime·sighandler(int32 sig, Siginfo *info, void *context, G *gp)
runtime·dumpregs(r);
}
- runtime·breakpoint();
runtime·exit(2);
}