VSCode java Debugger (v0.52.0) ignores break points and instead breaking in platform classes for now reason #1364

Activity

1. testforstephen commented on Jul 14, 2023

   

   Jinbo Wang (testforstephen)

   on Jul 14, 2023

   Contributor

   More actions

   Instead it is breaking in the platform Executor class where no breakpoints are defined

   This seems to be a problem with the source mapping rather than the breakpoint. The breakpoint stops at the correct position, but some of the stack frames show “Unknown Source” in the CALL STACK view. As a result, the cursor skips to the first frame that has a valid source mapping.
2. Jinbo Wang (testforstephen)

   self-assigned this

   on Jul 14, 2023
3. Jinbo Wang (testforstephen)

   added

   sourcemap

   on Jul 14, 2023
4. rgrunber commented on May 21, 2024

   

   Roland Grunberg (rgrunber)

   on May 21, 2024

   Last edited by rgrunber

   More actions

   Jinbo Wang (@testforstephen) , I have a sample project where someone is getting "Unknown Source" for source & library code and it ultimately sets the cursor in something like Thread.run(), but no one else is getting the issue. Are there any behaviours that would cause this ? I also noticed the first time the project is being debugged, there's a download job to fetch the sources, so maybe if that fails, it might cause this ?

   Update: Apparently it's happening in a remove scenario but works correctly locally.
5. testforstephen commented on May 22, 2024

   

   Jinbo Wang (testforstephen)

   on May 22, 2024

   Contributor

   More actions

   The debugger searches the source container associated with the project to locate the source file corresponding to the specified frame location. If no match is found, it returns the label ‘Unknown Source’.

   https://github.com/microsoft/java-debug/blob/83403a458e0d01fba5a3871fea81af742460bdf0/com.microsoft.java.debug.plugin/src/main/java/com/microsoft/java/debug/plugin/internal/JdtSourceLookUpProvider.java#L393
6. github-actions commented on Nov 10, 2025

   

   github-actionsbot

   on Nov 10, 2025 – with GitHub Actions

   More actions

   Hi Max Chernyshov (@mchern), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

   The debugger is currently known to skip breakpoints outside the main debugged class when attaching to a JVM without explicit source mappings. Suggestions:

   • Ensure your classes are compiled with debug symbols (javac –g).
   • Add sourcePaths in your attach config so VS Code can map sources, e.g.:

   {
     "type": "java",
     "name": "Attach to Remote",
     "request": "attach",
     "hostName": "localhost",
     "port": 5005,
     "sourcePaths": ["${workspaceFolder}/src/main/java"]
   }

   High-confidence references:
   • #1319: Debugger skips breakpoints not in the main class tracked #1319
   • #1116: Breakpoints ignored in other classes (Maven modules) #1116

   Other references with low confidence

   • (none additional)

   The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
7. github-actions

   added

   ai-triaged

   bug

   duplicate

   on Nov 10, 2025
8. github-actions

   closed this as not plannedon Nov 10, 2025