PenaDevops/delve
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Documentation/faq: Correct commands in substitute-path section (#3222)

Browse Source 
The text of the substitute-path section in the FAQ ("Can not set
breakpoints or see source listing in a complicated debugging
environment") mentions the command 'config help substitute-path', but
'help' is not a valid argument to the 'config' command.

Use 'help config' instead, which does mention 'substitute-path' and how
to set it.

Also, the command to list source files is 'sources', not 'source'. Fix
that.
This commit is contained in:
Philippe Blain 2022-12-15 03:02:06 -05:00 committed by GitHub
parent 9523849883
commit 72c77b1c30
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/faq.md
View File

@ -103,8 +103,8 @@ Command failed: open /path/to/the/mainfile.go: no such file or directory
This is not a bug. The Go compiler embeds the paths of source files into the executable so that debuggers, including Delve, can use them. Doing any of the things listed above will prevent this feature from working seamlessly.
The substitute-path feature can be used to solve this problem, see `config help substitute-path` or the `substitutePath` option in launch.json.
The substitute-path feature can be used to solve this problem, see `help config` or the `substitutePath` option in launch.json.
The `source` command could also be useful in troubleshooting this problem, it shows the list of file paths that has been embedded by the compiler into the executable.
The `sources` command could also be useful in troubleshooting this problem, it shows the list of file paths that has been embedded by the compiler into the executable.
If you still think this is a bug in Delve and not a configuration problem, open an [issue](https://github.com/go-delve/delve/issues), filling the issue template and including the logs produced by delve with the options `--log --log-output=rpc,dap`.