From be393aca57c1a4d85b6a14a85acef72252344067 Mon Sep 17 00:00:00 2001 From: Cuong Manh Le Date: Mon, 23 Oct 2023 10:56:57 +0700 Subject: [PATCH] runtime: document GODEBUG panicnil values Updates #25448 Change-Id: Ia1b7a376f5175f67e14ad4bd065d6e8ad5250d38 Reviewed-on: https://go-review.googlesource.com/c/go/+/536955 Reviewed-by: Keith Randall Reviewed-by: Keith Randall Reviewed-by: Carlos Amedee LUCI-TryBot-Result: Go LUCI Auto-Submit: Keith Randall --- src/runtime/extern.go | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/runtime/extern.go b/src/runtime/extern.go index 4b3ae63fb5c944..e42122fd3a1cd1 100644 --- a/src/runtime/extern.go +++ b/src/runtime/extern.go @@ -152,6 +152,9 @@ It is a comma-separated list of name=val pairs setting these named variables: risk in that scenario. Currently not supported on Windows, plan9 or js/wasm. Setting this option for some applications can produce large traces, so use with care. + panicnil: setting panicnil=1 disables the runtime error when calling panic with nil + interface value or an untyped nil. + runtimecontentionstacks: setting runtimecontentionstacks=1 enables inclusion of call stacks related to contention on runtime-internal locks in the "mutex" profile, subject to the MutexProfileFraction setting. When runtimecontentionstacks=0, contention on