GFuzz | Fuzzing concurrent Go programs

by system-pclub Go Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions Vulnerabilities Install Support

kandi X-RAY | GFuzz Summary

GFuzz is a Go library. GFuzz has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Our paper presents GFuzz, a dynamic detector for channel-related concurrency bugs in Go programs. For artifact evaluation, we release. Item (1) can be checked out by executing the following commands. Items (2), (3), (4) and (5) are released using a Google Sheet file asplos-710-artifact. Particularly, (2), (3) and (4) are related to Table 2 in the paper, and (5) is to provide more information for Table 3 in the paper. All columns and tabs discussed later are in the Google Sheet file, unless otherwise specified. Item (6) is to reproduce Figure 5 in the paper.

Support

Quality

Security

License

Reuse

Support

GFuzz has a low active ecosystem.

It has 2 star(s) with 1 fork(s). There are 5 watchers for this library.

It had no major release in the last 6 months.

There are 4 open issues and 1 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of GFuzz is current.

Quality

GFuzz has no bugs reported.

Security

GFuzz has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

GFuzz is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

GFuzz releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of GFuzz

Get all kandi verified functions for this library.

GFuzz Key Features

No Key Features are available at this moment for GFuzz.

GFuzz Examples and Code Snippets

No Code Snippets are available at this moment for GFuzz.

Community Discussions

No Community Discussions are available at this moment for GFuzz.Refer to stack overflow page for discussions.

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install GFuzz

You can download it from GitHub.

Support

Let's set up GCatch using a Docker environment. Now we are in a Docker terminal, the following commands are all executed inside this Docker environment. Additionally, all bugs being detected by GFuzz can be found in Tab Table-2-Bug. For testing grpc: All grpc packages start with google.golang.org/grpc. If the bug is located in grpc folder internal/resolver, then the module path would be google.golang.org/grpc/internal/resolver. For testing etcd: All etcd packages start with go.etcd.io/etcd/.../v3. For example, if the bug is located in etcd folder tests/integration/snapshot, then the module path would be go.etcd.io/etcd/tests/v3/integration/snapshot. For testing Kubernetes: All Kubernetes packages start with k8s.io/kubernetes. For example, if the bug is located in Kubernets folder pkg/kubelet/nodeshutdown/systemd, then the module path is: k8s.io/kubernetes/pkg/kubelet/nodeshutdown/systemd. For testing Prometheus: All Prometheus packages start with github.com/prometheus/prometheus. For example, if the bug is located in Prometheus folder storage/remote, then the module path is: github.com/prometheus/prometheus/storage/remote. For testing go-Ethereum: All go-Ethereum packages start with github.com/ethereum/go-ethereum/. For example, if the bug is located in Prometheus folder core, then the module path is: github.com/ethereum/go-ethereum/core. For testing tidb: For tidb module names, most tidb packages start with github.com/pingcap/tidb. For example, if the bug is located in tidb folder ./ddl/, then the module path is: github.com/pingcap/tidb/ddl. However, for bugs reported in badger, the module path is: github.com/pingcap/badger. For testing Moby(Docker): Docker fuzzing uses a slightly different routine. The Docker code must be stored in path /go/src/github.com/. If any bug was found from any programs above, GCatch would output a bug report similar to the following format.

Find more information at: