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
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
The handler for CMD_THREAD_CREATE hides "internal" threads from VSC (i.e. do not emit an event). An internal thread is one for which the name starts with "pydevd." or "ptvsd.". The handlers for the other 3 thread events (_KILL, _SUSPEND, _RUN) currently do not hide internal thread events. This means that the debug client (e.g. VSC) may be confused when it receives, for example, a stopped event for a thread it does not know about.
Either internal threads should always be hidden or they should never be.
The text was updated successfully, but these errors were encountered:
In my change, I am making sure that we only report about the thread that are in the map. They should get added to the map only if the are not "pydevd" or "ptvsd" threads.
The handler for
CMD_THREAD_CREATE
hides "internal" threads from VSC (i.e. do not emit an event). An internal thread is one for which the name starts with "pydevd." or "ptvsd.". The handlers for the other 3 thread events (_KILL
,_SUSPEND
,_RUN
) currently do not hide internal thread events. This means that the debug client (e.g. VSC) may be confused when it receives, for example, astopped
event for a thread it does not know about.Either internal threads should always be hidden or they should never be.
The text was updated successfully, but these errors were encountered: