Opened 3 years ago
Last modified 3 months ago
#22878 new defect
Trunnel needs a debug mode
| Reported by: | teor | Owned by: | |
|---|---|---|---|
| Priority: | Medium | Milestone: | |
| Component: | Core Tor/Trunnel | Version: | |
| Severity: | Normal | Keywords: | |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
I'm trying to diagnose a bug that occurs in trunnel/tor code, but it only occurs in shadow. Trunnel returns error strings, but doesn't log them, making it hard to work out which part of the code is causing the issue.
What I'd like to be able to do is define a macro when compiling to activate debug logging.
Child Tickets
Change History (2)
comment:1 Changed 12 months ago by
| Owner: | nickm deleted |
|---|---|
| Status: | new → assigned |
comment:2 Changed 3 months ago by
| Status: | assigned → new |
|---|
Change tickets that are assigned to nobody to "new".
Note: See
TracTickets for help on using
tickets.
These tickets are not things I'm currently working on. They may be important, but they don't need to be done by me specifically. Un-assigning.