You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
remote debugger unable to convert path correctly in different operating system #23688
Platform:Linux s97712 4.18.10-arch1-1-ARCH deps: update openssl to 1.0.1j #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:
It doesn't work, nothing happend when reach breakpoint.
I inspect the devtools through chrome://inspect/#pages
the devtools check the operating system with Host.isWin() , but it check the local operating system, not remote
Thanks for nice bug report.
This issue is fixed in latest Node 10.12 (node uses file urls in protocol instead of platform specific paths) and Chrome >= 71. You can try to use Chrome Canary on Windows.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
addaleax commentedon Oct 16, 2018
@nodejs/v8-inspector
eugeneo commentedon Oct 16, 2018
This is a Chrome DevTools issue. CC: @aslushnikov
alexkozy commentedon Oct 16, 2018
Thanks for nice bug report.
This issue is fixed in latest Node 10.12 (node uses file urls in protocol instead of platform specific paths) and Chrome >= 71. You can try to use Chrome Canary on Windows.
targos commentedon Oct 16, 2018
It looks like we landed the fix too soon? Should we revert until Chrome 71 is stable?
alexkozy commentedon Oct 16, 2018
Would it be possible to reland it in 6 weeks? It looks like Node 10 will go to LTS before.
Revert SGTM.
targos commentedon Oct 17, 2018
Sure. I suppose #22251 is the PR? Do we need to revert all 3 commits?
Trott commentedon Nov 29, 2018
What's the status of this?
github-actions commentedon Jun 27, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 28, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.