<mattip>
needhelp's traceback shows that VSCode is vendoring debugpy, which uses pydevd underneath
<mattip>
the pypi page for pydevd states it is used by PyDev, PyCharm, as well, so I wonder how PyCharm works and VSCode crashes
needshelp has joined #pypy
<needshelp>
mattip: i have no idea, its started to happen for me after an update with vscode,
<needshelp>
Which probably triggered the issue,
<needshelp>
Tried to revert to older version of vscode still happened. Maybe there is a file/directory that needs to be reverted where downgrade doesn't change.
<needshelp>
With pycharm well, their updates are less frequent so i don't have an issue with it
<mattip>
ok. I wonder where the best place to open an issue would be: VSCode, debugpy, or pydevd.
<mattip>
maybe pydevd?
<needshelp>
I'm opening a ticket now in pypy issue feed.
<needshelp>
I'm not really sure where the error occurs,
<needshelp>
the traceback related it to pypy itself
<fijal>
mattip: did you see my suggestion to run pydevd test suite with low jit threshold and see if it's a reproducer?
<fijal>
I don't think I have it in me, but seems like running pydevd (or even setting trace function directly on all threads) while running stuff surely might explode