mirror of
https://github.com/golang/go
synced 2024-11-15 07:30:28 -07:00
69e75c8581
This CL causes the printing of panic values to ensure that all newlines in the output are immediately followed by a tab, so that there is no way for a maliciously crafted panic value to fool a program attempting to parse the traceback into thinking that the panic value is in fact a goroutine stack. See https://github.com/golang/go/issues/64590#issuecomment-1932675696 + release note Updates #64590 Updates #63455 Change-Id: I5142acb777383c0c122779d984e73879567dc627 Reviewed-on: https://go-review.googlesource.com/c/go/+/581215 Auto-Submit: Alan Donovan <adonovan@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Michael Pratt <mpratt@google.com>
8 lines
359 B
Markdown
8 lines
359 B
Markdown
## Runtime {#runtime}
|
|
|
|
The traceback printed by the runtime after an unhandled panic or other
|
|
fatal error now indents the second and subsequent lines of the error
|
|
message (for example, the argument to panic) by a single tab, so that
|
|
it can be unambiguously distinguished from the stack trace of the
|
|
first goroutine. See [#64590](/issue/64590) for discussion.
|