Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #30012

Closed
Open
Created Apr 04, 2019 by teor@teor

When stem receives a signal, log useful information

In #30011 (moved), when stem hangs in Tor's CI, we kill it.

But that doesn't give us much information. To fix #29437 (moved), we need stem to log a backtrace when it receives a signal. (Or switch into debug mode, or something.)

You can pick any signal you like: maybe SIGUSR2 for debug logs, and SIGABRT for a stacktrace? (If you want stem to be like tor.)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking