Skip to content

Signal-trap table #22

Closed
Closed

Description

@graydon

OS signals currently don't get trapped properly, nor do we have a timer thread that interrupts a runaway task. Add such, using a flag to indicate a pending signal. Put a check at preemption points (fn entries and loop edges).

Activity

  1. graydon commented on Jun 23, 2010

    @graydon
    ContributorAuthor

    Added preemption points and a timer. No other-kinds of signals yet.

  2. graydon commented on Feb 15, 2012

    @graydon
    ContributorAuthor

    Obsolete. We'll use uv to pick up OS signals (hopefully!) and and explicit communication primitives for this.

  3. added a commit that references this issue on Dec 12, 2017
  4. added a commit that references this issue on Sep 13, 2019
  5. added a commit that references this issue on Dec 9, 2021
  6. added a commit that references this issue on Oct 13, 2023
  7. added 2 commits that reference this issue on Dec 4, 2023
  8. added a commit that references this issue on Dec 5, 2023
  9. added a commit that references this issue on Dec 5, 2023
  10. added 2 commits that reference this issue on Nov 11, 2025
  11. added a commit that references this issue on Sep 3, 2026
  12. added a commit that references this issue on Oct 8, 2026
  13. added a commit that references this issue on Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions