Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #9299

Closed (moved)
Open
Opened Jul 19, 2013 by Nick Mathewson@nickm🐙

Dump stack traces on assertion, crash, or general trouble

It's so easy to dump stack traces these days!

I have a "backtrace" branch right now that an dump stack traces on assertion failures. It works on glibc/ELF, and on OSX. We should expand it to work on Windows too, and BSD if we can.

Other fixes to make before it's ready:

  • It should be able to log a stack trace too.
    • It should log the stack trace on an assertion.
  • There should be an option to tell it not to log to the stack_dumps file, perhaps.
  • Perhaps the logfile should be pid-controlled?
  • It should support Windows.
  • It should handle deadly signals (SEGV, etc) as well.
  • It should indicate to the user somehow (if it can) that stuff might be saved to the stack_dumps file.
  • It should have tests.
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: 0.2.5.x-final
Milestone
Tor: 0.2.5.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#9299