Debugging Go does not work
See original GitHub issuecode-server
version:
$ code-server --version
server/development linux-x64 node-v8.15.0
- OS Version:
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
...
Description
Cannot debug Go. It stays in a loop for a while, cannot find any log failures.
Steps to Reproduce
- Start the server and log in
- Write a go file
- Add a breakpoint somewhere
- Click “debug”
- Hit “run”
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (4 by maintainers)
Top Results From Across the Web
debugging - Golang Debugger Not Running - Stack Overflow
The error is because you are trying to debug non main package. Debug the file from main package if you have settings to...
Read more >Debugging Go with VS Code - LogRocket Blog
Debugging is used to detect and fix faults in programs, preventing them from performing incorrectly after being deployed to production.
Read more >Debugger Stops Working : GO-6853 - YouTrack
If I open a go project, debugging seems to work fine. However, after multiple debug runs, it stops picking up breakpoints. The only...
Read more >Breakpoints not working (macos) · Issue #2244 - GitHub
Create a source file main.go; Set a breakpoint anywhere; Try to run/debug, either with default launch settings or something simple like. { "name ......
Read more >Debugging Go Code with GDB
You can generate uncompressed debug information by using go build -ldflags=-compressdwarf=false . (For convenience you can put the -ldflags option in the ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Will fix ASAP!
I appreciate the quick work on this. Sorry for my delay. The environment that I am working on has a kernel that is too old to support Ubuntu 18, so I had to fork this repo and back port to Ubuntu 16. I’ll try to merge these changes soon and let you know if it fixed it for me.