Skip to content

Conversation

@Jake-Shadle
Copy link
Collaborator

  • Handle non-SIGSTOP signals
  • Add failed attempt to test

This just implements the code pointed out in #124. I attempted to add a test for this by starting another named thread and sending a SIGHUP to it before spawning the dumper, but I don't think this scenario will ever result in the new code being run.

Resolve: #124

@Jake-Shadle Jake-Shadle force-pushed the handle-non-sigstop-signals branch from 6ce1b43 to 11618a4 Compare August 19, 2024 13:49
@gabrielesvelto
Copy link
Contributor

LGTM, merge whenever you want. BTW if you want to cut a new release we'll merge it quickly in Firefox as there's a lot of desirable changes that have been made lately.

@Jake-Shadle Jake-Shadle merged commit b43c79a into main Aug 20, 2024
@Jake-Shadle Jake-Shadle deleted the handle-non-sigstop-signals branch August 20, 2024 10:09
@Jake-Shadle
Copy link
Collaborator Author

I can cut a release after lunch.

@gabrielesvelto
Copy link
Contributor

Thanks a lot 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Adjust how we deal with pending signals when stopping threads on Linux

3 participants