tree a3c8272f920ce183ce2e9b150ef59893c2b02159
parent f78c016d5a67c7f7a4f7916193ca3204e2693cf5
author Hana (Hyang-Ah) Kim <hyangah@gmail.com> 1600884986 -0400
committer Hyang-Ah Hana Kim <hyangah@gmail.com> 1601070432 +0000

[release] src/goLanguageServer.ts: include sanitized trace to issue report

Many automated gopls crash reports come with empty stack trace
and provides little information. This CL tries to extract
the stack trace from panic or the initialize error message.
The stack trace is from the gopls binary itself so
there is not much confidential except the package file paths.
Remove those file paths and leave only the file base name
parts. The package paths are included in the function name
parts, so we still can locate the corresponding files in the
gopls repository.

If we fail to sanitize, do not include any stack trace
and ask users to include it manually.

Also, includes the language server binary flag, which will
help with identifying crashes caused by incorrect gopls args.
B

Change-Id: I5fcab48b28b7adb0adf369af4227c29ca646b2a3
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/256878
Trust: Hyang-Ah Hana Kim <hyangah@gmail.com>
Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
TryBot-Result: kokoro <noreply+kokoro@google.com>
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
(cherry picked from commit 9ebcc1fe739107f1f0e9ae6ad2d2d53e459dbb8a)
Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/257604