nodejs/node

remote debugger unable to convert path correctly in different operating system

Open

#23,688 创建于 2018年10月16日

在 GitHub 查看
 (7 评论) (0 反应) (0 负责人)JavaScript (117,218 star) (35,535 fork)batch import
help wantedinspector

描述

  • Version:v10.9.0
  • Platform:Linux s97712 4.18.10-arch1-1-ARCH #1 SMP PREEMPT Wed Sep 26 09:48:22 UTC 2018 x86_64 GNU/Linux
  • Subsystem:remote debugger

I debugger node on window, but my node server on linux. When I set the breakpoint through chrome devtools, like the below: image It doesn't work, nothing happend when reach breakpoint.

I inspect the devtools through chrome://inspect/#pages image

the devtools check the operating system with Host.isWin() , but it check the local operating system, not remote image

image

贡献者指南

技术栈
nodejsjavascript
领域
developer experience
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.js debugger internalscross platform path handling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
50
研究方向
Investigate the remote debugger path conversion in Node.js. The issue reports that Chrome DevTools incorrectly uses the local OS (Host.isWin()) instead of the remote Node.js OS when setting breakpoints, causing breakpoints to fail on Linux when debugging from Windows. Look at the inspector protocol and Node.js's debugger module (e.g., `lib/internal/inspector agent.js`) to understand how paths are converted. Determine if Node.js can provide the remote OS type to the devtools frontend or if the path conversion should be handled differently.