-
Notifications
You must be signed in to change notification settings - Fork 147
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
Debugger hides traceback/error message and doesn't naviagate to package source when justMyCode: false #1773
Comments
I'm facing the same issue, but in my case, it's due to a missing path: |
Would it be possible to get a setting in launch.json to re-enable this? this choice is quite annoying since most if the time the exceptions i'm debugging happen in library code. |
You'd have to ask VS code for that. It's not something that debugpy can control/change. |
Type: Bug
"justMyCode": false
in launch.jsonThere seem to be 2 possibly related issues happening here:
Note: i can do the following steps to see the big red box of traceback for the package which raised it:
PS: i also noticed that i'm unable to step over or continue execution on exceptions, which used to be possible (this would close the debugger with the exception being printed normally to stderr if its uncaught).
VS Code version: Code 1.94.1 (e10f2369d0d9614a452462f2e01cdc4aa9486296, 2024-10-05T05:44:32.189Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (68)
(2 theme extensions excluded)
The text was updated successfully, but these errors were encountered: