Proposal: pin specific thread(s) when debugging #140845
Labels
debug
Debug viewlet, configurations, breakpoints, adapter issues
feature-request
Request for new features or functionality
Milestone
Background
Multithreading is getting trend these days. Each debug session creates a bunch of independent PCs walking around the code. However, VSCode seems to lack the ability to focus on just a few threads rather than all threads in a process.
Pains
Each time I want to perform a step-through to a PC, I have to find that thread from Debug->Call Stack->specific thread that marked "Paused on step". And then I hover the curser on the tiny "step-in" icon and carefully press the button. When I settle down my mouse, the stack frame suddenly shows up at the other location! I have to carefully redo that nonsense. Sometimes, the stack frame stays relatively stable, but after I get used to the click-click muscle inertia, the stack relocates and fools me clicking the wrong frame!
Suggestion
Please make those frames stable or reserve shortcuts for frame-debugging. It would be a plus by supporting users to pin one or more interested frames. Those shortcuts should only affect those pinned frames. The pinned frames should be sorted in pin-time order.
The text was updated successfully, but these errors were encountered: