Skip to content

[fork/release/1.4] Dump each goroutine stack as a separate log message - #11

Merged
kevpar merged 1 commit into
fork/release/1.4from
backport-dump-stacks
Dec 7, 2020
Merged

kevpar merged 1 commit into
fork/release/1.4from
backport-dump-stacks

Conversation

@kevpar

@kevpar kevpar commented Dec 7, 2020

Copy link
Copy Markdown
Owner

This changes the stack dumping code so that we split the giant string
containing every goroutine's stack and log each stack as a separate log
message. This makes the output easier to parse, and especially helps in
cases where the log output is sent through a system with a log message
size limit, such as Windows's ETW.

Signed-off-by: Kevin Parsons kevpar@microsoft.com
(cherry picked from commit dbb117b)
Signed-off-by: Kevin Parsons kevpar@microsoft.com

This changes the stack dumping code so that we split the giant string
containing every goroutine's stack and log each stack as a separate log
message. This makes the output easier to parse, and especially helps in
cases where the log output is sent through a system with a log message
size limit, such as Windows's ETW.

Signed-off-by: Kevin Parsons <kevpar@microsoft.com>
(cherry picked from commit dbb117b)
Signed-off-by: Kevin Parsons <kevpar@microsoft.com>
@kevpar
kevpar merged commit 17959a9 into fork/release/1.4 Dec 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants