-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to start debugger - undefined symbol: AttachDebuggerTracing #669
Comments
This is an new issues on debugpy 1.4.0 (which is released on today 22 JUL) so you need to rollback to debugpy 1.3.0 |
I can confirm I also got the same error when I tried to run and debug Python scripts in VS Code. However, I did not install debugpy before (there is no such library in my pip3 list). Is there any way to roll back the built-in (I guess?) debugpy in VS Code? Or I should pip3 install 1.3.0 so that VS Code would use 1.3.0 instead of its built-in debugpy? Thanks for any help. |
@Clifford-Yen You can get the previous version by going to older version of the extension: |
Thanks @karthiknadig. I actually also checked it in the extension, but debugpy is also not there. That's why I am so confused. |
This issue occurs on different setups. See #670 for example |
As a note, I believe that setting an environment variable such as:
should make the debugging work again (without downgrading). I still haven't been able to reproduce it myself (so, if someone with that issue can report back if that works it'd be nice...). |
I have added the following line to the . |
Great... Can you also provide the logging for when the error happens? It's possible to collect that information by setting the following environment variables:
(replacing the |
The log files stays somehow empty. Here what the terminal shows:
|
The issue is that on unsupported platforms (such as aarch64/arm) it ended up doing a |
This has been fixed in the Locally you have 2 choices until it's featured in an official release:
Which will make it so that the native library is not loaded (the fix makes this happen automatically instead of failing in platforms where the library is not available).
The library name format is:
The files below may be used as a basis (flags may differ based on your platform, but in general they should be pretty close). |
Environment data
Actual behavior
Expected behavior
The debug server starts running
Steps to reproduce:
pip install debugpy
python -m debugpy --listen 5678 ./main.py
Is this a known issue with the M1 architecture? I am able to get this running successfully on an older macbook pro
The text was updated successfully, but these errors were encountered: