diff options
| author | Nick Mathewson <nickm@torproject.org> | 2005-06-08 21:47:42 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2005-06-08 21:47:42 +0000 |
| commit | bab2643b78d51ff1ea0a4a008b64a17af7ae64c0 (patch) | |
| tree | 3520e13b61cb13353235c558d1568e3363971d84 | |
| parent | eb11b8132fc695982b8bc3bba361dca18b379e0b (diff) | |
| download | tor-bab2643b78d51ff1ea0a4a008b64a17af7ae64c0.tar.gz tor-bab2643b78d51ff1ea0a4a008b64a17af7ae64c0.zip | |
Update item status
svn:r4359
| -rw-r--r-- | doc/TODO | 12 |
1 files changed, 7 insertions, 5 deletions
@@ -16,13 +16,15 @@ For 0.1.0.x: - Why do solaris cpuworks go dormant? (Apparently, disabling threads fixes this.) - Why does kevent barf with EINVAL on some freebsd boxes? + (Lucky is trying a patch that should tell us why.) - Fix the remaining flyspray bugs marked for 0.1.0.9 + (Only 124 remains.) - Free remaining unfreed memory (arma will run valgrind) - . Note libevent/method/platform combos that are unlikely to work. - o Write - - Test - - Backport - - Memory use on Linux: what's happening? + (Not for a stable release) + o Note libevent/method/platform combos that are unlikely to work. + . Memory use on Linux: what's happening? + - Is it threading? (Maybe, maybe not) + - Is it the buf_shrink bug? (Quite possibly) - instrument the code to figure out where our memory is going. (all platforms?) - change torrc to point to abuse-faq (once abuse-faq is posted) |