microsoft / microsoft/vscode-java-debug
Debugger is using old cached test file
Offen
@testforstephen arbeitet bereits daran.
Seit 20.5.2018.
ai-triaged
bug
external
sourcemap
voting
- Vorherrschende Sprache
- TypeScript
- Sterne
- 591
- Forks
- 429
- Ø Merge
- 1 T. 9 Std.
- Gemergte PRs (30 T.)
- 19
Beschreibung
When I set a breakpoint and use the debugger, it opens an old cached version of the source file
Environment
- Operating System: Windows 8 and 10 (recently upgraded, got the same issue on both)
- JDK version: java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode) - Visual Studio Code version: 1.23.1
- Java extension version: Java extension pack 0.3.0
- Java Debugger extension version: 0.9.0
Steps To Reproduce
- Check out a simple single module maven project.
- Set a breakpoint in VSCode in one of the tests.
- Use
mvn -Dmaven.surefire.debug testto run the test. Stops atListening for transport dt_socket at address: 5005 - Attach the debugger to port 5005. Everything works fine the first time.
- Continue working on the project (edit, compile, test code). Possibly days later run the debugger again using the same workflow.
- It uses an old cached file. The actual source file: (Note the file path and breakpoint at line 280)

Cick on top call stack item in vscode debug panel shows some older cached version of the file (note file path in AppData/Local/Temp):

This used to work fine a couple of months ago.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Bewertung
Dieses Issue wurde noch nicht bewertet.