tree b75d130f5edf0f96a23f68d7af8e131833f70d69
parent e0a2c5d4b540934e06867710fe7137661a2a39ec
author Russ Cox <rsc@golang.org> 1298493733 -0500
committer Russ Cox <rsc@golang.org> 1298493733 -0500
golang-hg 618f3bf366985c4ebb58695444d892851fbcbe87

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