Opened 6 years ago

Last modified 2 years ago

#10817 new task

Write instructions for using valgrind with the debian tor

Reported by: arma Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.7
Severity: Normal Keywords: tor-relay, lorax, SponsorS-deferred valgrind debug debian
Cc: Actual Points:
Parent ID: Points: small
Reviewer: Sponsor:

Description

In #9754 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?

Child Tickets

Change History (21)

comment:1 Changed 5 years ago by nickm

Keywords: 025-triaged 025-deferrable lorax added

Nice to have if somebody writes it, but okay to defer.

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

We can merge this whenever it gets done, but 0.2.5 doesn't wait for it.

comment:3 Changed 4 years ago by nickm

Milestone: Tor: 0.2.???Tor: 0.2.7.x-final

These may be worth looking at for 0.2.7.

comment:4 Changed 4 years ago by nickm

Status: newassigned

comment:5 Changed 4 years ago by nickm

Keywords: 027-triaged-1-deferrable added

Marking tickets as deferrable from 0.2.7 triage round-1

comment:6 Changed 4 years ago by isabela

Keywords: SponsorS added
Points: small
Priority: normaltrivial
Version: Tor: 0.2.7

comment:7 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.8.x-final

comment:8 Changed 4 years ago by nickm

Keywords: SponsorS removed
Sponsor: SponsorS

Bulk-replace SponsorS keyword with SponsorS sponsor field in Tor component.

comment:9 Changed 4 years ago by nickm

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

Move a bunch of (but not all) low-priority items to 0.2.???. If you write a patch, it can still get into 0.2.8

comment:10 Changed 3 years ago by isabela

Sponsor: SponsorSSponsorS-can

comment:11 Changed 3 years ago by nickm

Keywords: SponsorS-deferred added
Sponsor: SponsorS-can

Remove the SponsorS status from these items, which we already decided to defer from 0.2.9. add the SponsorS-deferred tag instead in case we ever want to remember which ones these were.

comment:12 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:13 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:14 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:15 Changed 2 years ago by nickm

Keywords: 025-triaged removed

remove an old triage keyword.

comment:16 Changed 2 years ago by nickm

Keywords: 027-triaged-in added

comment:17 Changed 2 years ago by nickm

Keywords: 027-triaged-in removed

comment:18 Changed 2 years ago by nickm

Keywords: 027-triaged-1-deferrable removed

comment:19 Changed 2 years ago by nickm

Keywords: 025-deferrable removed

comment:20 Changed 2 years ago by nickm

Status: assignednew

Change the status of all assigned/accepted Tor tickets with owner="" to "new".

comment:21 Changed 2 years ago by nickm

Keywords: valgrind debug debian added
Severity: Normal
Note: See TracTickets for help on using tickets.