<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>debugging on Golang</title><link>https://golang.k5kc.com/tags/debugging/</link><description>Recent content in debugging on Golang</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sun, 16 Aug 2020 00:10:00 +0530</lastBuildDate><atom:link href="https://golang.k5kc.com/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Debugging</title><link>https://golang.k5kc.com/2020/08/16/debugging/</link><pubDate>Sun, 16 Aug 2020 00:10:00 +0530</pubDate><guid>https://golang.k5kc.com/2020/08/16/debugging/</guid><description>No one can write bug-free code, so debugging is a requisite skill for every software engineer. Here are some tips about debugging Go programs:
(1) Print
Yes! Printing logs seems the easiest method, but it is indeed the most effective approach in most cases. Go has provided a big family of printing functions in fmt package, and using them neatly is an expertise you should grasp.
(2) Debugger
In some scenarios, maybe you need the specialized debugger tools to help you spot the root cause.</description></item></channel></rss>