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 }}
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.
On Windows 10 , building a Linux docker container, add the files to a subfolder such as x/y/z
run the container with security-options="seccomp=unconfined' (and an entrypoint running dlv as follows:
dlv test --headless --listen=:2345 --log=true --api-version=1 )
In VSCODE, make sure the files you are debugging are also in a local c:<workspace>\x\y\z (otherwise breakpoint matching does not work ever anyway).
In launch.json set the remotePath to "/" (see below)
With verbose logging, note that the breakpoint cannot be set or verified, because it translates the path to C:<workspace>\x\y\z (windows file separator)
Repeat the process adding the source files instead to a subfolder eg /src/x/y/z
Set remote path to /src/
Breakpoints now work because VSCode translates the breakpoint path to Linux file separated absolute path.
________________________________
From: Ramya Rao<mailto:notifications@github.com>
Sent: 11/21/2018 4:07 AM
To: Microsoft/vscode-go<mailto:vscode-go@noreply.github.com>
Cc: Frank Szendzielarz<mailto:Frank@franks.technology>; Author<mailto:author@noreply.github.com>
Subject: Re: [Microsoft/vscode-go] remotePath of '/' when debugging remote linux container translates breakpoint paths to windows local paths (#2119)
Repeat the process adding the source files instead to a subfolder eg /src/x/y/z
You do this in the container or on Windows?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#2119 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Af9nzg3HqLD-l-k4_ZxLjOq4J5_JRJxRks5uxMN4gaJpZM4Ybg6T>.
This has been fixed in the latest update to the Go extension (0.11.7)
Thanks @quoctruong for the fix (PR 2794) & thanks @FrankSzendzielarz for logging the issue.
On Windows 10 , building a Linux docker container, add the files to a subfolder such as x/y/z
run the container with security-options="seccomp=unconfined' (and an entrypoint running dlv as follows:
dlv test --headless --listen=:2345 --log=true --api-version=1 )
In VSCODE, make sure the files you are debugging are also in a local c:<workspace>\x\y\z (otherwise breakpoint matching does not work ever anyway).
In launch.json set the remotePath to "/" (see below)
With verbose logging, note that the breakpoint cannot be set or verified, because it translates the path to C:<workspace>\x\y\z (windows file separator)
Repeat the process adding the source files instead to a subfolder eg /src/x/y/z
Set remote path to /src/
Breakpoints now work because VSCode translates the breakpoint path to Linux file separated absolute path.
{
The text was updated successfully, but these errors were encountered: