Open Source Go Debuggers

Find and debug your most painful performance issues across code, infrastructure and CI/CD pipelines. Let you tag your data on the dimensions important for your organization. Allows you to store large volumes of high cardinality profiling data cheaply and efficiently. FlameQL enables custom queries to select and aggregate profiles quickly and efficiently for easy analysis. Analyze application performance profiles using our suite of profiling tools. Understand usage of CPU and memory resources at any point in time and identify performance issue before your customer do. Collect, store, and analyze profiles from various external profiling tools in one central location. Link to your Open Telemetry tracing data and get request-specific or span-specific profiles to enhance other observability data like traces and logs.

Delve is a debugger for the Go programming language. The goal of the project is to provide a simple, full featured debugging tool for Go. Delve should be easy to invoke and easy to use. Chances are if you're using a debugger, things aren't going your way. With that in mind, Delve should stay out of your way as much as possible. Delve aims to be a very simple and powerful tool, but can be confusing if you're not used to using a source level debugger in a compiled language. This document will provide all the information you need to get started debugging your Go programs. The first CLI subcommand we will explore is debug. This subcommand can be run without arguments if you're in the same directory as your main package, otherwise it optionally accepts a package path.

q is a better way to do print statement debugging. For best results, dedicate a terminal to tailing $TMPDIR/q while you work. You also can simply tail -f $TMPDIR/q, but it's highly recommended to use the provided commands. Type q.Q instead of fmt.Printf and your variables will be printed like the provided example. Faster to type, pretty-printed vars and expressions. Easier to see inside structs, doesn't go to noisy-ass stdout. It goes to $TMPDIR/q. q Go offers pretty colors!

BotKube is a messaging bot for monitoring and debugging Kubernetes clusters. It's built and maintained by InfraCloud. BotKube can be integrated with multiple messaging platforms like - Slack, Mattermost, Microsoft Teams to help you monitor your Kubernetes cluster(s), debug critical deployments and gives recommendations for standard practices by running checks on the Kubernetes resources. BotKube watches Kubernetes resources and sends a notification to the channel if any event occurs for example a ImagePullBackOff error. You can customize the objects and level of events you want to get from the Kubernetes cluster. You can turn on/off notifications simply by sending a message to @BotKube. BotKube can execute kubectl commands on Kubernetes cluster without giving access to Kubeconfig or underlying infrastructure. With BotKube you can debug your deployment, services or anything about your cluster right from your messaging window.

GAPID is a developer tool for recording and inspecting calls made by an application to the graphics driver. Once a capture of a target application has been made, GAPID lets you disconnect from the target and inspect all the graphics commands made by the application. GAPID is able to replay the command stream, letting you visualize the frame composition by stepping through each command and inspecting the driver state at any point in the stream. Replay also supports modifications, allowing you to adjust command parameters and shader source to instantly see what effect this would have on the frame. GAPID can also visualize the textures, shaders and draw call geometry used by the application.

Package errors provides simple error handling primitives. The traditional error handling idiom in Go that is applied recursively up the call stack results in error reports without context or debugging information. The errors package allows programmers to add context to the failure path in their code in a way that does not destroy the original value of the error. Wrap function returns a new error that adds context to the original error. Using errors.Wrap constructs a stack of errors, adding context to the preceding error. Depending on the nature of the error it may be necessary to reverse the operation of errors.Wrap to retrieve the original error for inspection. Any error value which implements this interface can be inspected by errors.Cause. errors.Cause will recursively retrieve the topmost error which does not implement causer, which is assumed to be the original cause.

git-bug is fully embedded in git, you only need your git repository to have a bug tracker. git-bug is distributed. Use your normal git remote to collaborate, push and pull your bugs! git-bug works offline, in a plane or under the sea? Keep reading and writing bugs! It prevents vendor lock-in: your usual service is down or went bad? You already have a full backup. It is fast, listing bugs or opening them is a matter of milliseconds. git-bug doesn't pollute your project, no files are added in your project. git-bug integrates with your tooling, use the UI you like (CLI, terminal, web) or integrate with your existing tools through the CLI or the GraphQL API. git-bug bridges to other bug trackers. Use bridges to import and export to other trackers. An interactive terminal UI is available using the command git bug termui to browse and edit bugs.