2022-02-09
1708
#go
Popoola Temitope
91822
Feb 9, 2022 â‹… 6 min read

Debugging Go with VS Code

Popoola Temitope I'm a software developer and technical writer. I love learning about new technology and am always ready to share ideas with others.

Recent posts:

Build A Custom React Native Turbo Module For Android

Build a custom React Native Turbo Module for Android

Build a React Native Turbo Module for Android to access device info like model, IP, uptime, and battery status using native mobile APIs.

Emmanuel John
Feb 27, 2025 â‹… 8 min read
how to measure round-trip time using cURL

How to measure round-trip time (RTT) using cURL

Learn how to measure round-trip time (RTT) using cURL, a helpful tool used to transfer data from or to a server.

David Omotayo
Feb 26, 2025 â‹… 10 min read

React.memo explained: When to use it (and when not to)

React.memo prevents unnecessary re-renders and improves performance in React applications. Discover when to use it, when to avoid it, and how it compares to useMemo and useCallback.

Emmanuel John
Feb 26, 2025 â‹… 9 min read
React useCallback: When And How To Use It For Better Performance

React useCallback: When and how to use it for better performance

Learn how React’s useCallback hook boosts performance by memoizing functions and preventing unnecessary re-renders with practical examples and best practices.

Emmanuel John
Feb 26, 2025 â‹… 6 min read
View all posts

4 Replies to "Debugging Go with VS Code"

  1. This is an absolutely incredible tutorial, it works with VSCode Devcontainer as well btw – I had a really hard time finding a proper tutorial but this one finally got it working. Thank you sir!

  2. Install -v githup.com/go-delve/cmd/dlv@latest
    I think here it needs to be
    go Install -v githup.com/go-delve/cmd/dlv@latest

  3. Couldn’t really easily follow the tutorial as it claimed. A number of the information was a little misleading, eg:
    1. Install Delve extension in VS Code is not correct, it is actually to perform Go Install on the delve package.
    2. the instruction on what one should see in the VS code didn’t match what I saw on my VS Code which was version 1.70.2, I needed to figure out how to get there.
    3. Setting up condition breakpoint should not include the curly brackets. BTW, why did you give an example that wouldn’t work ? The code was having variable “userinfos”, your example of conditional breakpoint used variable “user”

  4. Thank you, this was actually really helpful. Didn’t think that it would actually work since it’s a random post, but hey here we are.

Leave a Reply