x/tools/gopls: crash in mapPosition computing OutgoingCalls to unsafe.Slice · Issue #66923 · golang/go · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.
@ceearrashee Thanks for the report. It looks like browsing outgoing call hierarchy triggered the panic. Can you tell us more about when you observed this crash?
Were you checking the function or method named SetCap?
Did you notice other errors or problems before this crash? (code navigation not functioning, squiggles indicating problems in the code, etc)
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Apr 19, 2024
I can reproduce this by computing a call hierarchy involving a call to unsafe.Slice.
These special functions cause no end of bugs.
adonovan
changed the title
x/tools/gopls: crash mapping positions in OutgoingCalls
x/tools/gopls: crash in mapPosition computing OutgoingCalls to unsafe.Slice
Apr 19, 2024
Uh oh!
There was an error while loading. Please reload this page.
gopls version: v0.15.3/go1.22.2
gopls flags:
update flags: proxy
extension version: 0.41.2
environment: Visual Studio Code win32
initialization error: undefined
issue timestamp: Thu, 18 Apr 2024 19:20:56 GMT
restart history:
Thu, 18 Apr 2024 18:12:44 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.
Please attach the stack trace from the crash.
A window with the error message should have popped up in the lower half of your screen.
Please copy the stack trace and error messages from that window and paste it in this issue.
Failed to auto-collect gopls trace: no gopls log.
gopls stats -anon
{ "DirStats": { "Files": 5496, "TestdataFiles": 0, "GoFiles": 413, "ModFiles": 1, "Dirs": 383 }, "GOARCH": "amd64", "GOOS": "windows", "GOPACKAGESDRIVER": "", "GOPLSCACHE": "", "GoVersion": "go1.22.2", "GoplsVersion": "v0.15.3", "InitialWorkspaceLoadDuration": "5.9188475s", "MemStats": { "HeapAlloc": 135173400, "HeapInUse": 197967872, "TotalAlloc": 1481395568 }, "WorkspaceStats": { "Files": { "Total": 4366, "Largest": 6161825, "Errs": 0 }, "Views": [ { "GoCommandVersion": "go1.22.2", "AllPackages": { "Packages": 876, "LargestPackage": 279, "CompiledGoFiles": 4437, "Modules": 157 }, "WorkspacePackages": { "Packages": 108, "LargestPackage": 61, "CompiledGoFiles": 487, "Modules": 1 }, "Diagnostics": 0 } ] } }OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
The text was updated successfully, but these errors were encountered: