golang/go

os/signal: No access to the siginfo_t struct

Open

#9,764 opened on Feb 3, 2015

View on GitHub
 (16 comments) (1 reaction) (1 assignee)Go (19,008 forks)batch import
FeatureRequestcompiler/runtimehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

The siginfo_t struct that is delivered with signals contains various useful information about the signal. In some cases, this information is necessary to implement the kernel API of various features. For example, fcntl(F_SETLEASE) requires that your process receive a SIGIO when the lock is broken, and the si_fd field in the siginfo_t struct tells you what filehandle the kernel is notifying your process about.

Please provide an interface that will allow Go code to access the information in the siginfo_t struct.

Contributor guide

Research direction
Investigate how signals are handled in the Go runtime (runtime/os linux.go, runtime/signal *.go) and how siginfo t is currently discarded. Look at the os/signal package to understand where to add a new API to expose siginfo fields. Consider using cgo or runtime internals to capture the siginfo t structure and provide access via Go types.
Tech stack
go
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GoUnix signalsC
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30