Skip to content

There is a pattern where signal names are not correctly retrieved on Linux #3434

@ryuichi1208

Description

@ryuichi1208

When a child process dies due to a signal such as SIGABRT, the signal name and signal number may not be displayed correctly and may become invalid.

The following is the log when sending SIGABRT to a child process. gunicorn is using the latest version 23.0.0.

Worker (pid:74) was sent code 134!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions