On Fri, Nov 12, 2010 at 5:49 PM, Paul Menzel <paulepan...@users.sourceforge.net> wrote: > Dear Tor folks, > > > I noticed that Tor had crashed on my system. I am using Debian Lenny > with Tor 0.2.1.26-1~~lenny+1. The only thing I could find out about this > crash is the following line running `dmesg`. > > $ dmesg > […] > [Several of these Treason uncloaked messages as you can see some > seconds before the crash. I obfuscated the IP addresses.] > [3301769.746795] TCP: Treason uncloaked! Peer > xxx.xxx.xxx.xxx:60659/42859 shrinks window 1343914705:1343916145. Repaired. > [3413085.371871] TCP: Treason uncloaked! Peer > yyy.yyy.yyy.yyy:19595/45969 shrinks window 2416591117:2416591857. Repaired. > [3604257.970658] tor[22506]: segfault at 21d4fc5 ip 7f1e78ba4ea6 sp > 41188920 error 4 in libcrypto.so.0.9.8[7f1e78b21000+172000] > [3604257.970707] type=1701 audit(1289305397.030:2): auid=4294967295 > uid=102 gid=104 ses=4294967295 pid=22506 comm="tor" sig=11 > > So it could also be libcrypto is the culprit. `libssl0.9.8` is running > with `0.9.8g-15+lenny8` as version. > > Is that a known problem? What other information can I provide to solve > that? Unfortunately I have not found out how to reproduce it yet.
Without more information, there's not much info to go on there to diagnose the problem. Generally, to debug a segfault, we need a stack trace. To get one of those, make sure you're running Tor with coredumps enabled, and use gdb to get a trace if Tor crashes again. There are some decent online docs on how to do this; a little searching should turn them up. (You can ignore the "Treason Uncloaked!" junk. That's the Linux kernel being overly dramatic about peers that don't do TCP windows right or something.) hth, -- Nick *********************************************************************** To unsubscribe, send an e-mail to majord...@torproject.org with unsubscribe or-talk in the body. http://archives.seul.org/or/talk/
