Opened 9 years ago

Closed 8 years ago

Last modified 7 years ago

#1520 closed defect (user disappeared)

segmentation fault on 0.2.2.13-alpha

Reported by: seeess Owned by:
Priority: Low Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version: Tor: 0.2.2.13-alpha
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

tor --version
Jun 02 13:09:57.142 [notice] Tor v0.2.2.13-alpha (git-feb8c1b5f67f2c6f). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Tor version 0.2.2.13-alpha (git-feb8c1b5f67f2c6f).

grep -v '#' torrc
Log notice file /var/log/tor/notices.log
Nickname sandvine
RelayBandwidthRate 1400 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 2000 KBytes # But allow bursts up to 200KB/s (1600Kbps)
ContactInfo seeess
ExitPolicy reject *:* # no exits allowed
ORPort 8888
DirPort 8889
NumCPUs 2
ConnLimit 8192
DirReqStatistics 1
CellStatistics 1
EntryStatistics 1
ExtraInfoStatistics 1

gdb tor core.907

warning: Can not parse XML syscalls information; XML support was disabled at compile time.
GNU gdb (Gentoo 7.0.1 p1) 7.0.1
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /usr/local/bin/tor...done.
[New Thread 20151]
[New Thread 20150]

warning: Can't read pathname for load map: Input/output error.

warning: .dynamic section for "/usr/lib/libssl.so.0.9.8" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/libpthread.so.0" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib/libc.so.6" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/ld-linux.so.2" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/libresolv.so.2" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libevent-1.4.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libevent-1.4.so.2
Reading symbols from /usr/lib/libssl.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.8
Reading symbols from /usr/lib/libcrypto.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.8
Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1
Error while mapping shared library sections:
fÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ®íþÿYíþÿÏíþÿfÝþÿfÝþÿfÝþÿßþÿfÝþÿkèþÿèþÿfÝþÿfÝþÿ(èþÿkèþÿkèþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ~èþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ²èþÿÐèþÿëèþÿfÝþÿfÝþÿfÝþÿ: No such file or directory.
Core was generated by `tor'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7eaff7b in dtls1_accept () from /usr/lib/libssl.so.0.9.8
(gdb)

warning: Can't read pathname for load map: Input/output error.

warning: .dynamic section for "/usr/lib/libssl.so.0.9.8" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/libpthread.so.0" is not at the expected address (wrong library or version mismatch?)

warning: .dynamic section for "/lib/libc.so.6" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/ld-linux.so.2" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations

warning: .dynamic section for "/lib/libresolv.so.2" is not at the expected address

warning: difference appears to be caused by prelink, adjusting expectations
Reading symbols from /lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libz.so.1
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libevent-1.4.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libevent-1.4.so.2
Reading symbols from /usr/lib/libssl.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libssl.so.0.9.8
Reading symbols from /usr/lib/libcrypto.so.0.9.8...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcrypto.so.0.9.8
Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libresolv.so.2
Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libnss_files.so.2
Reading symbols from /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/libgcc_s.so.1
Error while mapping shared library sections:
fÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ®íþÿYíþÿÏíþÿfÝþÿfÝþÿfÝþÿßþÿfÝþÿkèþÿèþÿfÝþÿfÝþÿ(èþÿkèþÿkèþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ~èþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿfÝþÿ²èþÿÐèþÿëèþÿfÝþÿfÝþÿfÝþÿ: No such file or directory.
Core was generated by `tor'.
Program terminated with signal 11, Segmentation fault.
#0 0xb7eaff7b in dtls1_accept () from /usr/lib/libssl.so.0.9.8

tail -n 100 /var/log/tor/notices.log
May 28 11:53:39.979 [warn] Our clock is 6 minutes, 21 seconds behind the time published in the consensus network status document (2010-05-28 16:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 11:53:39.979 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 11:53:39.979 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 12:00:00.546 [notice] We now have enough directory information to build circuits.
May 28 12:53:38.478 [warn] Our clock is 6 minutes, 22 seconds behind the time published in the consensus network status document (2010-05-28 17:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 12:53:38.478 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 12:53:38.478 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 13:00:07.553 [notice] We now have enough directory information to build circuits.
May 28 13:53:36.700 [warn] Our clock is 6 minutes, 24 seconds behind the time published in the consensus network status document (2010-05-28 18:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 13:53:36.700 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 13:53:36.700 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 14:00:05.160 [notice] We now have enough directory information to build circuits.
May 28 14:53:36.652 [warn] Our clock is 6 minutes, 24 seconds behind the time published in the consensus network status document (2010-05-28 19:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 14:53:36.652 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 14:53:36.652 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 15:00:01.436 [notice] We now have enough directory information to build circuits.
May 28 15:53:37.001 [warn] Our clock is 6 minutes, 24 seconds behind the time published in the consensus network status document (2010-05-28 20:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 15:53:37.001 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 15:53:37.001 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 16:00:04.403 [notice] We now have enough directory information to build circuits.
May 28 16:53:41.210 [warn] Our clock is 6 minutes, 19 seconds behind the time published in the consensus network status document (2010-05-28 21:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 16:53:41.210 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 16:53:41.210 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 17:00:04.358 [notice] We now have enough directory information to build circuits.
May 28 17:53:37.776 [warn] Our clock is 6 minutes, 23 seconds behind the time published in the consensus network status document (2010-05-28 22:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 17:53:37.776 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 17:53:37.776 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 18:00:01.477 [notice] We now have enough directory information to build circuits.
May 28 18:53:36.052 [warn] Our clock is 6 minutes, 25 seconds behind the time published in the consensus network status document (2010-05-28 23:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 18:53:36.052 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 18:53:36.052 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 19:00:09.005 [notice] We now have enough directory information to build circuits.
May 28 19:53:35.811 [warn] Our clock is 6 minutes, 25 seconds behind the time published in the consensus network status document (2010-05-29 00:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 19:53:35.811 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 19:53:35.811 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 20:00:04.488 [notice] We now have enough directory information to build circuits.
May 28 20:53:33.417 [warn] Our clock is 6 minutes, 27 seconds behind the time published in the consensus network status document (2010-05-29 01:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 20:53:33.417 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 20:53:33.417 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 21:00:00.154 [notice] We now have enough directory information to build circuits.
May 28 21:53:33.301 [warn] Our clock is 6 minutes, 27 seconds behind the time published in the consensus network status document (2010-05-29 02:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 21:53:33.301 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 21:53:33.301 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 22:00:07.886 [notice] We now have enough directory information to build circuits.
May 28 22:53:32.789 [warn] Our clock is 6 minutes, 28 seconds behind the time published in the consensus network status document (2010-05-29 03:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 22:53:32.789 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 22:53:32.789 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 28 23:00:03.861 [notice] We now have enough directory information to build circuits.
May 28 23:53:30.914 [warn] Our clock is 6 minutes, 30 seconds behind the time published in the consensus network status document (2010-05-29 04:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 28 23:53:30.914 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 28 23:53:30.914 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 00:00:10.109 [notice] We now have enough directory information to build circuits.
May 29 00:53:29.869 [warn] Our clock is 6 minutes, 31 seconds behind the time published in the consensus network status document (2010-05-29 05:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 00:53:29.869 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 00:53:29.869 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 01:00:01.936 [notice] We now have enough directory information to build circuits.
May 29 01:54:30.358 [warn] Our clock is 5 minutes, 30 seconds behind the time published in the consensus network status document (2010-05-29 06:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 01:54:30.358 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 01:54:30.358 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 02:00:09.126 [notice] We now have enough directory information to build circuits.
May 29 02:54:28.326 [warn] Our clock is 5 minutes, 32 seconds behind the time published in the consensus network status document (2010-05-29 07:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 02:54:28.326 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 02:54:28.326 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 03:00:00.153 [notice] We now have enough directory information to build circuits.
May 29 03:54:27.913 [warn] Our clock is 5 minutes, 33 seconds behind the time published in the consensus network status document (2010-05-29 08:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 03:54:27.913 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 03:54:27.913 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 04:00:02.501 [notice] We now have enough directory information to build circuits.
May 29 04:54:27.472 [warn] Our clock is 5 minutes, 33 seconds behind the time published in the consensus network status document (2010-05-29 09:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 04:54:27.472 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 04:54:27.472 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 05:00:01.243 [notice] We now have enough directory information to build circuits.
May 29 05:54:27.111 [warn] Our clock is 5 minutes, 33 seconds behind the time published in the consensus network status document (2010-05-29 10:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 05:54:27.111 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 05:54:27.111 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 06:00:02.360 [notice] We now have enough directory information to build circuits.
May 29 06:54:25.674 [warn] Our clock is 5 minutes, 35 seconds behind the time published in the consensus network status document (2010-05-29 11:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 06:54:25.674 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 06:54:25.674 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 07:00:09.589 [notice] We now have enough directory information to build circuits.
May 29 07:54:24.300 [warn] Our clock is 5 minutes, 36 seconds behind the time published in the consensus network status document (2010-05-29 12:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 07:54:24.300 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 07:54:24.300 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 08:00:00.789 [notice] We now have enough directory information to build circuits.
May 29 08:54:23.525 [warn] Our clock is 5 minutes, 37 seconds behind the time published in the consensus network status document (2010-05-29 13:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 08:54:23.525 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 08:54:23.525 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 09:00:03.387 [notice] We now have enough directory information to build circuits.
May 29 09:54:22.406 [warn] Our clock is 5 minutes, 38 seconds behind the time published in the consensus network status document (2010-05-29 14:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 09:54:22.407 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 09:54:22.407 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 10:00:05.279 [notice] We now have enough directory information to build circuits.
May 29 10:54:22.030 [warn] Our clock is 5 minutes, 39 seconds behind the time published in the consensus network status document (2010-05-29 15:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 10:54:22.030 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 10:54:22.030 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 11:00:07.634 [notice] We now have enough directory information to build circuits.
May 29 11:54:21.497 [warn] Our clock is 5 minutes, 39 seconds behind the time published in the consensus network status document (2010-05-29 16:00:00 GMT). Tor needs an accurate clock to work correctly. Please check your time and date settings!
May 29 11:54:21.497 [notice] Our directory information is no longer up-to-date enough to build circuits: We have no recent network-status consensus.
May 29 11:54:21.497 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent network-status consensus.
May 29 12:00:06.928 [notice] We now have enough directory information to build circuits.

Child Tickets

Change History (9)

comment:1 Changed 9 years ago by seeess

uhh yeah i forgot the trace didn't I

(gdb) bt
#0 0xb7eaff7b in dtls1_accept () from /usr/lib/libssl.so.0.9.8
#1 0xb7eaa218 in ssl23_get_client_hello () from /usr/lib/libssl.so.0.9.8
#2 0xb7eaa35a in ssl23_get_client_hello () from /usr/lib/libssl.so.0.9.8
#3 0xb7ea9d7c in ssl3_send_finished () from /usr/lib/libssl.so.0.9.8
#4 0xb7eaad66 in ssl23_connect () from /usr/lib/libssl.so.0.9.8
#5 0xb7ea7598 in ?? () from /usr/lib/libssl.so.0.9.8
#6 0xb2a87598 in ?? ()
#7 0x00000017 in ?? ()
#8 0x9fbf3518 in ?? ()
#9 0x00004000 in ?? ()
#10 0x00000000 in ?? ()

comment:2 Changed 9 years ago by nickm

Well that's downright bizarre. "dlts1_accept()" is only supposed to get called for the DTLS protocol, which Tor doesn't even use (it's a datagram encryption protocol for use with UDP). What version of openssl do you have?

comment:3 Changed 9 years ago by seeess

openssl version
OpenSSL 0.9.8n 24 Mar 2010

comment:4 Changed 9 years ago by nickm

Milestone: Tor: 0.2.2.x-final
Priority: normalminor

Still very very strange. Have you been able to reproduce this at all? If it occurs with any regularity, you could try running Tor under valgrind to see if there are any memory corruption problems.

comment:5 Changed 9 years ago by nickm

Version: Tor: 0.2.2.x-finalTor: 0.2.2.13-alpha

comment:6 Changed 9 years ago by nickm

Any more information on this one? Has it happened again? Is the stack trace in the dlts1_*() thing every time, or other places too? Did you get a chance to try valgrind or some similar tool?

comment:7 Changed 8 years ago by Sebastian

Resolution: user disappeared
Status: newclosed

Please reopen if you learn more.

comment:8 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:9 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.