From d94a8c56adcd83572345f6136d609f488b9c58a8 Mon Sep 17 00:00:00 2001 From: Florian Lehner Date: Mon, 20 Oct 2025 20:09:21 +0200 Subject: [PATCH] runtime: cleanup pagetrace pagetrace functionality was removed with CL 583379. Change-Id: I8e8718e6cf5415e326ec127fb294588866ee4e6a Reviewed-on: https://go-review.googlesource.com/c/go/+/713260 Reviewed-by: Michael Knyszek LUCI-TryBot-Result: Go LUCI Reviewed-by: David Chase --- src/runtime/extern.go | 7 ------- 1 file changed, 7 deletions(-) diff --git a/src/runtime/extern.go b/src/runtime/extern.go index 62dab74bc0..c35aef0662 100644 --- a/src/runtime/extern.go +++ b/src/runtime/extern.go @@ -171,13 +171,6 @@ It is a comma-separated list of name=val pairs setting these named variables: silently default to 1024. Future versions of Go may remove this limitation and extend profstackdepth to apply to the CPU profiler and execution tracer. - pagetrace: setting pagetrace=/path/to/file will write out a trace of page events - that can be viewed, analyzed, and visualized using the x/debug/cmd/pagetrace tool. - Build your program with GOEXPERIMENT=pagetrace to enable this functionality. Do not - enable this functionality if your program is a setuid binary as it introduces a security - 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. -- 2.52.0