Linux workstation

Upstream software project

golang-bugsnag-panicwrap

Go library for catching and handling panics in Go applications

About golang-bugsnag-panicwrap

Go library for catching and handling panics in Go applications

This project links 4 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

golang-bugsnag-panicwrap repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.golang-bugsnag-panicwrap: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
golang-bugsnag-panicwrap
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13, fedora-43, fedora-44
License expression
MIT
Metadata completeness
100/100 (not a software quality rating)
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Panicwrap is a Go library that re-executes a Go binary and monitors stderr output from the binary for a panic. When it find a panic, it executes a user-defined handler function. Stdout, stderr, stdin, signals, and exit codes continue to work as normal, making the existence of panicwrap mostly invisble to the end user until a panic actually occurs. Since a panic is truly a bug in the program meant to crash the runtime, globally catching panics within Go applications is not supposed to be possible. Despite this, it is often useful to have a way to know when panics occur. panicwrap allows you to do something with these panics, such as writing them to a file, so that you can track when panics occur. Panicwrap is not a panic recovery system. Panics indicate serious problems with your application and should crash the runtime. panicwrap is just meant as a way to monitor for panics. If you still think this is the worst idea ever, read the section below on why. This package contains the source code needed for building packages that reference the following Go import paths: – github.com/bugsnag/panicwrap

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. golang-github-bugsnag-panicwrap-dev

    Debian 12 (Bookworm) / golang / source golang-bugsnag-panicwrap

    1.2.0-2

    Go library for catching and handling panics in Go applications

    allbookworm

Debian 13 (Trixie)

  1. golang-github-bugsnag-panicwrap-dev

    Debian 13 (Trixie) / golang / source golang-bugsnag-panicwrap

    1.2.0-2

    Go library for catching and handling panics in Go applications

    alltrixie

Fedora 43

  1. golang-github-bugsnag-panicwrap-devel

    Fedora 43 / Unspecified / source golang-github-bugsnag-panicwrap

    1.3.4-8.fc43

    Go library for catching and handling panics in Go applications

    noarch43

Fedora 44

  1. golang-github-bugsnag-panicwrap-devel

    Fedora 44 / Unspecified / source golang-github-bugsnag-panicwrap

    1.3.4-10.fc44

    Go library for catching and handling panics in Go applications

    noarch44

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.