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 }}
Repository navigation
Frame skipped when debugging during step-in, but justMyCode is false #630
OS and version: macOS 15.3.1, VSCode Devcontainer mcr.microsoft.com/devcontainers/python:3.13-bookworm
Python version (& distribution if applicable, e.g. Anaconda): 3.13.1
Using VS Code or Visual Studio: VSCode 1.97.2
Actual behavior
I reach a breakpoint in my own code and press "step into." I receive a message that says
Frame skipped from debuging during step-in. Note: may have been skipped because of "justMyCode" option (default==true). Try setting "justMyCode": false in the debug configuration (e.g., launch.json).
Source: Attatch to Python
The debugger only goes to frames in my own code. It does not go to frames in my library code.
However, I have double and tripled checked that the debugpy.debugJustMyCode setting is false. I even completely restarted VSCode to verify, but it still skips all frames outside of my code.
Expected behavior
VSCode should not show me this message, and it should not skip frames. It should debug the code in the external library as directed.
Steps to reproduce:
Start VSCode
Go to the settings
Set the justMyCode setting to false
Restart VSCode
Go back to settings and verify the setting is still false
Set a breakpoint on a line of code that will call an external library.
Open a terminal
In my case I am working on a Django project and trying to debug a test case, so the command is debugpy manage.py test
Wait for the debugger to stop at the breakpoint
Press Step Into (F11)
Receive the frame skipped message even though justMyCode is false.
I'm going to guess you're doing an attach (at least your repro steps require an attach). This should be a dupe of #617 and would require a newer version of the vscode-python-debugger extension.
Activity
rchiodo commentedon Feb 24, 2025
I'm going to guess you're doing an attach (at least your repro steps require an attach). This should be a dupe of #617 and would require a newer version of the vscode-python-debugger extension.
eleanorjboyd commentedon Feb 24, 2025
should be fixed if its a duplicate of #617, comment if it isn't and I can reopen it. Thanks!