debug.copyStackTrace doesn't work when called outside the callstack context menu #140239
Labels
bug
Issue identified by VS Code Team member as probable bug
debug
Debug viewlet, configurations, breakpoints, adapter issues
insiders-released
Patch has been released in VS Code Insiders
Milestone
ivanhernandez13 commentedJan 6, 2022
Issue Type: Bug
I wanted to be able to copy the call stack through a keyboard shortcut so I created a binding for
debug.copyStackTracebut found that it doesn't do anything. I tried different combinations ofwhenclauses and ensured that my keystroke was not being captured by something else but still no luck.Invoking the command directly in my extension like so
vscode.commands.executeCommand('debug.copyStackTrace')also did not work and the thenable resolved toundefined.The comment here and post here imply this should work outside of the callstack context so I've filed this as a bug as opposed to a feature request for a keyboard shortcut to copy the call stack.
VS Code version: Code 1.63.2 (Universal) (899d46d, 2021-12-15T09:37:28.172Z)
OS version: Darwin x64 21.2.0
Restricted Mode: No
System Info
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (15)
A/B Experiments
The text was updated successfully, but these errors were encountered: