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
Currently it's achievable by setting a breakpoint condition like "(int)thread.gettid() == 5", but debuggers like LLDB support directly specifying thread id(s) for a breakpoint, which is much faster then evaluating the condition expression every time the breakpoint hits:
Syntax: breakpoint modify <cmd-options> [<breakpt-id | breakpt-id-list>]
-t <thread-id> ( --thread-id <thread-id> )
The breakpoint stops only for the thread whose TID matches this argument. The token
'current' resolves to the current thread's ID.
I am also interested in this feature. Looks like, we can use BreakpointMode to identify a thread when setting breakpoint. However, there is a problem, when I try to send CapabilitiesEvent with new breakpointModes, the VSCode ignore new values (registerBreakpointModes called once in initialize request). Does the VSCode team intend to improve the behavior of CapabilitiesEvent?
Activity
DrSergei commentedon Jun 3, 2025
I am also interested in this feature. Looks like, we can use
BreakpointModeto identify a thread when setting breakpoint. However, there is a problem, when I try to sendCapabilitiesEventwith newbreakpointModes, the VSCode ignore new values (registerBreakpointModescalled once in initialize request). Does the VSCode team intend to improve the behavior ofCapabilitiesEvent?