SetBreakpointsRequestHandler fails when supplied path is using forward slashes

Open

#318 opened on Feb 4, 2020 3 comments 0 reactions 1 assignee View on GitHub

@testforstephen is already working on this.

Since Feb 7, 2020.

Assessment

This issue has not been assessed yet.

Description

ai-triaged bug enhancement

Description
When a DAP (debug adapter protocol) client sends a setBreakpoints request with a path that contains forward slashes the breakpoint is not set.
The server also (wrongfully?) reports back that the command was executed successfully.

Observed behavior
The code runs without halting at the breakpoint.

Expected behavior
The program should halt at the breakpoint and send a breakpoint event to the DAP client.

Logging with forward slashes (Not working)

Sending: 
{
  "command": "setBreakpoints",
  "arguments": {
    "source": {
      "name": "Hello.java",
      "path": "c:/project/src/main/java/Hello.java"
    },
    "breakpoints": [
      {
        "line": 6
      }
    ],
    "sourceModified": false,
    "lines": [
      6
    ]
  },
  "type": "request",
  "seq": 3
}

Received:
{
  "type": "response",
  "seq": 4,
  "body": {
    "breakpoints": [
      {
        "message": "",
        "line": 6,
        "verified": null,
        "id": 1
      }
    ]
  },
  "command": "setBreakpoints",
  "request_seq": 3,
  "success": true
}

Logging with backward slashes (Working)

Sending: 
{
  "command": "setBreakpoints",
  "arguments": {
    "source": {
      "name": "Hello.java",
      "path": "c:\project\src\main\java\Hello.java"
    },
    "breakpoints": [
      {
        "line": 6
      }
    ],
    "sourceModified": false,
    "lines": [
      6
    ]
  },
  "type": "request",
  "seq": 3
}

Received:
{
  "type": "response",
  "seq": 4,
  "body": {
    "breakpoints": [
      {
        "message": "",
        "line": 6,
        "verified": true,
        "id": 1
      }
    ]
  },
  "command": "setBreakpoints",
  "request_seq": 3,
  "success": true
}

Suggestion
I think the "offending" code is here
This line behaves differently depending if forward or backward slashes have been used.
Maybe replace all forward slashes with backward slashes if we are on windows.
Could be implemented before/after the drive letter fix.

System
Windows 10
DAP Client: emacs with lsp-mode/dap-mode
DAP Server: jdtls (Eclipse language server)

Dominant language: Java
Stars: 409
Forks: 204
Avg merge: 1d 13h
Merged PRs (30d): 4

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug][UI] Change the method of opening the Action Detail Open

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

Netcracker/qubership-integration-platform#913 · Opened Sep 23, 2026
SEC-CORS-006 declares MEDIUM but can only emit HIGH or LOW Open

bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

jdubois/boot-ui#1100 · Opened Sep 23, 2026
build-scan-xunit: accept ISO offset timestamps in test reports Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

elastic/gradle-plugins#157 · Opened Sep 23, 2026
OpenAPI document marks optional request body of `PUT /api/users/me` as required Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

cryptomator/hub#497 · Opened Sep 23, 2026
No test covers the claim that only the last command's state is checked Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

johanhaleby/occurrent#1120 · Opened Sep 23, 2026

More Java issues