-
Notifications
You must be signed in to change notification settings - Fork 72
Closed as duplicate of#617
Closed as duplicate of#617
Copy link
Labels
triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Description
Environment data
- debugpy version: 1.8.12
- 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.
Metadata
Metadata
Assignees
Labels
triage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team