Bug 380183

Created attachment 105706 [details]
terminal log

Well, got at a stable hardened Gentoo Linux the following for tor-0.3.1.1_alpha:

t44 ~ # /etc/init.d/tor start
 * Starting tor ...
==8226== Memcheck, a memory error detector
==8226== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==8226== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info                                     
==8226== Command: /usr/bin/tor --hush --runasdaemon 1 --pidfile /var/run/tor/tor.pid                            
==8226==                                                                                                        
==8226== Use of uninitialised value of size 8                                                                   
==8226==    at 0x173F51: ??? (in /usr/bin/tor)                                                                  
==8226==    by 0x1AF645: ??? (in /usr/bin/tor)
==8226==    by 0x1B4FB4: router_parse_addr_policy_item_from_string (in /usr/bin/tor)
==8226==    by 0x177E68: ??? (in /usr/bin/tor)
==8226==    by 0x17804F: ??? (in /usr/bin/tor)
==8226==    by 0x1782CA: policies_parse_exit_policy (in /usr/bin/tor)
==8226==    by 0x1783EC: policies_parse_exit_policy_from_options (in /usr/bin/tor)
==8226==    by 0x17852D: validate_addr_policies (in /usr/bin/tor)
==8226==    by 0x200EF2: ??? (in /usr/bin/tor)
==8226==    by 0x205D0C: options_init_from_string (in /usr/bin/tor)
==8226==    by 0x2060E0: options_init_from_torrc (in /usr/bin/tor)
==8226==    by 0x156252: tor_init (in /usr/bin/tor)
==8226== 
...

==21116== Use of uninitialised value of size 8
==21116==    at 0x28506B: strmap_free (container.c:1428)
==21116==    by 0x299B22: prot_strings (sandbox.c:1262)
==21116==    by 0x299B22: install_syscall_filter (sandbox.c:1660)
==21116==    by 0x299B22: initialise_libseccomp_sandbox (sandbox.c:1836)
==21116==    by 0x299B22: sandbox_init (sandbox.c:1862)
==21116==    by 0x1592A0: tor_main (main.c:3728)
==21116==    by 0x150D17: main (tor_main.c:34)
==21116== 
--21116-- WARNING: unhandled amd64-linux syscall: 317
--21116-- You may be able to write your own handler.
--21116-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--21116-- Nevertheless we consider this a bug.  Please report
--21116-- it at http://valgrind.org/support/bug_reports.html.


And the last 2 lines forced me to file this bug.