This is driving me nuts. tor compiles fine but segfaults soon after starting. I
have googled and found similar complaints but no solution.
I tried tor-0.2.12-alpha after tor-0.2.0.34 showed this problem since the
changelog to the unstable versions refers to fixing a segfault on starting.
But unstable also shows exactly the same problem. By contrast, v0.1.2.18 built
on dsl and run without these issues some time ago, but that is quite old.
Details: tor-0.2.0.34 and tor-0.2.12-alpha compile fine on Damnsmalllinux
using gcc-3.3.5 (old I know). Installed in /opt/tor against libevent-1.3e and
openssl-0.9.8g which were also built and installed in that prefix. libc is
also old - think Debian Woody. Not running in daemon mode.
Here is what is is printed to the terminal:
<snip>
Feb 21 21:06:29.785 [notice] Parsing GEOIP file.
Feb 21 21:06:30.734 [notice] No current certificate known for authority moria1;
launching request.
Feb 21 21:06:30.734 [notice] No current certificate known for authority tor26;
launching request.
Feb 21 21:06:30.734 [notice] No current certificate known for authority dizum;
launching request.
Feb 21 21:06:30.734 [notice] No current certificate known for authority ides;
launching request.
Feb 21 21:06:30.734 [notice] No current certificate known for authority
gabelmoo; launching request.
Feb 21 21:06:30.734 [notice] No current certificate known for authority
dannenberg; launching request.
Feb 21 21:06:30.734 [notice] Bootstrapped 5%: Connecting to directory server.
Feb 21 21:06:30.734 [notice] Couldn't read /home/dsl/.tor/cached-descriptors;
trying to load routers from old location /home/dsl/.tor/cached-routers.
Feb 21 21:06:31.603 [notice] I learned some more directory information, but not
enough to build a circuit: We have no network-status consensus.
Feb 21 21:06:31.604 [notice] Bootstrapped 10%: Finishing handshake with
directory server.
./tor_wrap.sh: line 49: 29078 Segmentation fault /opt/tor/bin/tor -f
/home/dsl/.tor/torrc "$@"
</snip>
How do I fix this?
