Result for 821861B2FD62FEE45E3AF3E8BC2B77F2B095C97F

Query result

Key Value
FileName./usr/share/gocode/src/github.com/bugsnag/panicwrap/.goipath
FileSize46
MD5E7B6A0A89CCA661CCD0E61ED4D499730
SHA-1821861B2FD62FEE45E3AF3E8BC2B77F2B095C97F
SHA-256C3B39B97C6707288EF163CE2AD6A63E71872E3F938E1A403ED8F3390FCDBAD3C
SSDEEP3:WmWpWvAEeBy4zAGIV4n:WmAWKBy4zJIV4n
TLSH
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD562D238723EF67ED8BE44465580A72364
PackageArchnoarch
PackageDescriptionPanicwrap 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
PackageMaintainerFedora Project
PackageNamegolang-github-bugsnag-panicwrap-devel
PackageRelease7.fc33
PackageVersion1.2.0
SHA-1718C0EFA7ECD7E71589CE7E04057851E56FE554D
SHA-256644A339655FCBE6FDCD55DA4C1147EEC5D84792B09B90166AA7B0B9825C25003