Hello Roger,
I updated the ticket. You will find the output of the valgrind there as well: https://trac.torproject.org/projects/tor/attachment/ticket/22255/valgrind.tx...
best regards
Dirk
On 23.05.2017 06:00, Roger Dingledine wrote:
On Tue, May 23, 2017 at 03:01:10AM +0000, John Ricketts wrote:
Roger,
I have whatever resources you need for testing. Let me know if you would like them.
git clone https://git.torproject.org/git/tor cd tor.git ./autogen.sh && ./configure && make
- edit /etc/security/limits.conf to have "tord hard nofile 65536" and
"tord soft nofile 65536" lines, where tord is your user who will run it.
valgrind --leak-check=yes --error-limit=no --undef-value-errors=no src/or/tor orport 9001 dirport 9030 nickname sorryitsslow geoipfile src/config/geoip
(You might also want to set datadirectory, etc if you prefer, or point it to a torrc file if you prefer. Once you've got it working, you might run it with a datadirectory that has keys for an established relay.)
Then watch the output for interesting valgrind complaints (I don't expect any, but if you find some, great!), and when you've let it run for a while, ^C it, let it close down, and see if Valgrind tells you about any "definite" memory leaks.
Be aware that unless the CPU is super amazing, it will be totally cpu saturated and constantly failing to keep up with the requests it receives. So it is a fine thing to do for active bug hunting, but somewhat rude to do on real relays. :)
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays