logo
search
Back to Pixie
COLLAPSE ALL
  • Home
  • About Pixie
    • Pixie Overview
    • Data Sources
    • How Pixie uses eBPF
    • Roadmap
    • FAQ
    • Troubleshooting
  • Installing Pixie
    • Requirements
  • Using Pixie
    • Using the Live UI
    • Using the CLI
    • Using the API
  • Tutorials
  • Reference
    • Admin
      • Authentication
      • Debug Info
      • Deploy Options
      • Environment-Specific Configurations
      • Find a Cluster ID
      • Managing API Keys
      • Managing Deploy Keys
      • Tuning Memory Usage
      • Uninstalling Pixie
      • Updating Pixie
      • User Management & Sharing
      • Verifying Images
    • Architecture
WebsiteSlack Us

Debug Info

Pixie automatically traces requests of a variety of protocol types. A subset of the supported protocols and encryption libraries require debug information to work with Pixie.

Checking for debug symbols

You can verify that an executable has debug symbols using nm:

nm <executable>

An output of no symbols means the application has no debug symbols and won't be traced.

Checking for DWARF debug information

You can verify that an executable has DWARF debug information using dwarfdump or llvm-dwarfdump:

dwarfdump <executable>

An output of No DWARF information present means the application has no DWARF debug information, and won't be traced.

Adding debug information to your Golang executable

By default, go build compiles your program with debug information. However, if you compile with -ldflags, make sure to remove the '-s' and '-w'.

This site uses cookies to provide you with a better user experience. By using Pixie, you consent to our use of cookies.