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
  • #10817

Closed (moved)
Open
Opened Feb 06, 2014 by Roger Dingledine@arma

Write instructions for using valgrind with the debian tor

In #9754 (moved) we have a user experiencing weird heap corruption, or memory corruption, or who knows. It happened for a while and then it stopped happening.

If we'd had easier ways for normal Debian / Ubuntu users to run valgrind on their Tor, we might have gotten a more useful hint.

Also, we probably would have wanted it to be the Tor run the normal way, not a separate Tor run a different way.

Are there easy ways to do this? What's the right way to explain to a normal user how to do it?

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#10817