Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #31594
Closed
Open
Issue created Sep 03, 2019 by teor@teor

Close all the log fds before aborting

We should close the sigsafe_log_fds before abort(), so that we are less likely to lose log lines in the fd buffers.

Here are the abort() users:

  • tor_abort_()
  • crash_handler()
  • format_number_sigsafe()
  • raw_assert()
  • raw_assert_unreached_msg()
  • trunnel_abort()

We could:

  • define a raw_abort() function that closes the fds
  • use it instead of abort()
  • #define trunnel_abort() as raw_abort()
  • update our C linter to require raw_abort() instead of abort()
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking