microsoft / microsoft/vscode-java-debug

Debugger is using old cached test file

未关闭
#302 27 条评论 9 个 reaction 已指派 1 人 在 GitHub 查看

@testforstephen 已经在做这个了。

开始于 2018年5月20日。

ai-triaged bug external sourcemap voting
主要语言
TypeScript
星标
591
派生
429
平均合并
1 天 9 小时
30 天内合并 PR
19

描述

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
  1. Check out a simple single module maven project.
  2. Set a breakpoint in VSCode in one of the tests.
  3. Use mvn -Dmaven.surefire.debug test to run the test. Stops at Listening for transport dt_socket at address: 5005
  4. Attach the debugger to port 5005. Everything works fine the first time.
  5. Continue working on the project (edit, compile, test code). Possibly days later run the debugger again using the same workflow.
  6. It uses an old cached file. The actual source file: (Note the file path and breakpoint at line 280)
    image
    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):
    image

This used to work fine a couple of months ago.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。