Tor issueshttps://gitlab.torproject.org/tpo/core/tor/-/issues2020-06-27T14:11:14Zhttps://gitlab.torproject.org/tpo/core/tor/-/issues/98WSAENOBUFS: Running out of buffer space on Windows2020-06-27T14:11:14ZTracWSAENOBUFS: Running out of buffer space on Windows```
Feb 06 02:47:39.469 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
Feb 06 12:51:31.380 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
Feb 06 14:25:25.031 [err]...```
Feb 06 02:47:39.469 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
Feb 06 12:51:31.380 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
Feb 06 14:25:25.031 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
Feb 07 02:15:17.138 [err] do_main_loop(): poll failed: No buffer space available [WSAENOBUFS ] [10055]
```
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]
**Trac**:
**Username**: spy1Tor: unspecifiedhttps://gitlab.torproject.org/tpo/core/tor/-/issues/100installation problem2020-06-27T14:11:14ZTracinstallation problemHi,
I can´t get tor to install on an intel box running SuSE 9.1.
I am using tor-0.0.9.4.tar.gz. I do tar xzf tor-0.0.9.4.tar.gz,
then cd into the new directory, then do ./configure, which runs fine.
When I try to make, I get lots of ...Hi,
I can´t get tor to install on an intel box running SuSE 9.1.
I am using tor-0.0.9.4.tar.gz. I do tar xzf tor-0.0.9.4.tar.gz,
then cd into the new directory, then do ./configure, which runs fine.
When I try to make, I get lots of errors complaining about torgzip.c,
The output looks like this:
cc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c log.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c fakepoll.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c util.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c compat.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c container.c
rm -f libor.a
ar cru libor.a log.o fakepoll.o util.o compat.o container.o
ranlib libor.a
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c crypto.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c aes.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c tortls.c
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I/usr/local/ssl/include -g -O2 -Wall -g -O2 -c torgzip.c
torgzip.c:20:18: zlib.h: Datei oder Verzeichnis nicht gefunden
torgzip.c: In Funktion »is_gzip_supported«:
torgzip.c:35: error: `ZLIB_VERSION' undeclared (first use in this function)
torgzip.c:35: error: (Each undeclared identifier is reported only once
torgzip.c:35: error: for each function it appears in.)
(much more to follow)
zlib is installed:
# rpm -qa|grep zlib
zlib-1.2.1-70.6
I was able to install an old version of tor (tor-0.0.8.1.tar.gz), but when I
run it, it complains like this;
Feb 12 18:52:13.988 [err] You are running Tor version 0.0.8.1, which will not work with this network.
Is there a way to run and install tor for me?
Thanks for any help
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: thunderhttps://gitlab.torproject.org/tpo/core/tor/-/issues/101default tor installation does not work over wifi2020-06-27T14:11:14ZTracdefault tor installation does not work over wifii'm running mac os 10.3. and have my powerbook connected over an apple airport extreme basestation.
the default tor installation only gives me privoxy 503 errors - this might be a privoxy issue, i will report the issue there as well.
the...i'm running mac os 10.3. and have my powerbook connected over an apple airport extreme basestation.
the default tor installation only gives me privoxy 503 errors - this might be a privoxy issue, i will report the issue there as well.
the same tor installation however, works perfectly when i connect the powerbook over ehternet - it's when using wifi that i only 503's.
thanks
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: renehttps://gitlab.torproject.org/tpo/core/tor/-/issues/102CVS current crashes immediately on launch2020-06-27T14:11:14ZTracCVS current crashes immediately on launchStarting 2/23/2005, about 8PM EST, my CVS current builds are crashing upon launch. I have been anxiously awaiting CVS updates and have seen new code updates, but each new build crashes with the same message:
Feb 23 20:07:06.299 [notice...Starting 2/23/2005, about 8PM EST, my CVS current builds are crashing upon launch. I have been anxiously awaiting CVS updates and have seen new code updates, but each new build crashes with the same message:
Feb 23 20:07:06.299 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 23 20:07:23.037 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
Feb 23 20:10:22.315 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 23 20:10:38.381 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
Feb 23 20:41:42.167 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 23 20:42:02.705 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
Feb 24 05:28:28.573 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 24 05:28:42.900 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
Feb 24 06:25:16.627 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 24 06:25:31.073 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
Feb 24 11:31:29.223 [notice] Tor 0.1.0.0-alpha-cvs opening log file.
Feb 24 11:31:43.262 [err] connection.c:1580: assert_connection_ok: Assertion !conn->stream_id failed; aborting.
gdb backtrace gives:
#0 0x48217feb in kill () from /usr/lib/libc.so.12
#1 0x4828ca3f in abort () from /usr/lib/libc.so.12
legacy/trac#2 0x0805be68 in assert_connection_ok (conn=0x8122700, now=1109262703)
at connection.c:1649
legacy/trac#3 0x0806ba05 in conn_read_callback (fd=23, event=2, _conn=0x8122700)
at main.c:339
legacy/trac#4 0x481e8a8c in event_process_active () from /usr/lib/libevent.so.0
legacy/trac#5 0x481e8c35 in event_loop () from /usr/lib/libevent.so.0
legacy/trac#6 0x481e8ab6 in event_dispatch () from /usr/lib/libevent.so.0
legacy/trac#7 0x0806c915 in do_main_loop () at main.c:1027
legacy/trac#8 0x0806d2c5 in tor_main (argc=1, argv=0xbfbffb80) at main.c:1656
legacy/trac#9 0x0807d04f in main (argc=1, argv=0xbfbffb80) at tor_main.c:18
legacy/trac#10 0x0804baf2 in ___start ()
I'm running on netbsd 2.0_stable, P2-300 with 256M ram.
[Automatically added by flyspray2trac: Operating System: Other]
**Trac**:
**Username**: yancmhttps://gitlab.torproject.org/tpo/core/tor/-/issues/103Some Tor certs pick www.Nickname.com as their nickname2020-06-27T14:11:14ZTracSome Tor certs pick www.Nickname.com as their nicknameFeb 24 19:32:55.590 [warn] tor_tls_get_peer_cert_nickname(): Peer certificate nickname has illegal characters.
Feb 24 19:32:55.899 [warn] connection_tls_finish_handshake(): Other side (194.95.224.201:443) has a cert without a valid nickn...Feb 24 19:32:55.590 [warn] tor_tls_get_peer_cert_nickname(): Peer certificate nickname has illegal characters.
Feb 24 19:32:55.899 [warn] connection_tls_finish_handshake(): Other side (194.95.224.201:443) has a cert without a valid nickname. Closing.
Feb 24 19:51:52.199 [warn] tor_tls_get_peer_cert_nickname(): Peer certificate nickname has illegal characters.
Feb 24 19:51:52.199 [warn] connection_tls_finish_handshake(): Other side (194.95.224.201:443) has a cert without a valid nickname. Closing.
Feb 24 19:57:14.456 [warn] tor_tls_get_peer_cert_nickname(): Peer certificate nickname has illegal characters.
Feb 24 19:57:14.456 [warn] connection_tls_finish_handshake(): Other side (194.95.224.201:443) has a cert without a valid nickname. Closing.
Feb 24 21:48:52.162 [warn] tor_tls_get_peer_cert_nickname(): Peer certificate nickname has illegal characters.
Feb 24 21:48:52.162 [warn] connection_tls_finish_handshake(): Other side (194.95.224.201:443) has a cert without a valid nickname. Closing.
router NetWorkXXIII 194.95.224.201
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: thomass0.0.9.5Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/104Signals, threads, and libevent may not necessarily play nice2020-06-27T14:11:13ZNick MathewsonSignals, threads, and libevent may not necessarily play niceSometimes when you control-c a server, multiple threads all get a sigint, and handle it oddly.
<arma2> Feb 27 03:29:09.348 [notice] foo
<arma2> Feb 27 03:29:09.349 [notice] Interrupt: will shut down in 30 seconds. In
terrupt again to ex...Sometimes when you control-c a server, multiple threads all get a sigint, and handle it oddly.
<arma2> Feb 27 03:29:09.348 [notice] foo
<arma2> Feb 27 03:29:09.349 [notice] Interrupt: will shut down in 30 seconds. In
terrupt again to exit now.
<arma2> Feb 27 03:29:09.350 [notice] foo
<arma2> Feb 27 03:29:09.351 [notice] Sigint received a second time; exiting now.
<arma2> Feb 27 03:30:35.950 [notice] 1024
<arma2> Feb 27 03:30:35.966 [notice] Interrupt: will shut down in 30 seconds. In
terrupt again to exit now.
<arma2> Feb 27 03:30:35.967 [notice] 1024
<arma2> Feb 27 03:30:35.968 [notice] Sigint received a second time; exiting now.
<arma2> hm.
<arma2> ok, so, not a thread thing.
<arma2> looks like it's getting called twice.
<arma2> does lib event let you double-register?
<arma2> is your tor_get_thread_id() known to work?
> Haven't verified it, no, but it is Really Simple.
> And if it's broken, so is pthreads.
<arma2> ooook :)
<arma2> ah. how's this:
<arma2> i'm not sending a sigint,
<arma2> i'm typing !^c.
<arma2> do you suppose that matters?
<arma2> it does.
> ackpth!
<arma2> whee.
<arma2> is that threads or libevent?
* nickm has no idea what *that* means.
<arma2> are we not allowed to sig_ign a !^c?
> No, I think we are.
<arma2> does !^c sent a sigint to all threads?
<arma2> s/sent/send/
*** You have new email.
> Unspecified afaicr.
<arma2> 'woo'
> Threads and signals is one of the canonically fudgy areas of pthreads iirc.
<arma2> ok i did a kill -INT of a child, and it called hibernate-begin-exit
<arma2> they are not ignoring signals like we'd like them to.
> hmmmmm.
[Automatically added by flyspray2trac: Operating System: All]Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/105Todays Build - Possible memory leak?2020-06-27T14:11:13ZTracTodays Build - Possible memory leak?I sync'd and built against CVS this AM - Launched at 6:45 EST. Memory usage is at 25M and climbing.
I suspect a memory leak, but am unsure how to help you find it.
Will it crash at some point and generate a useful core?
I'm on NetBS...I sync'd and built against CVS this AM - Launched at 6:45 EST. Memory usage is at 25M and climbing.
I suspect a memory leak, but am unsure how to help you find it.
Will it crash at some point and generate a useful core?
I'm on NetBSD 2.0_Stable w/P2-300 256M Ram.
Process limits:
clarity 13 -> limit
cputime unlimited
filesize unlimited
datasize 131072 kbytes
stacksize 2048 kbytes
coredumpsize unlimited
memoryuse 251972 kbytes
memorylocked 83990 kbytes
maxproc 160
openfiles 1648
I'm also getting 6-10 of the following messages per hour:
Feb 28 13:55:08.261 [warn] circuit_receive_relay_cell(): connection_edge_process_relay_cell (away from origin) failed.
Feb 28 13:55:08.261 [warn] command_process_relay_cell(): circuit_receive_relay_cell (forward) failed. Closing.
[Automatically added by flyspray2trac: Operating System: BSD]
**Trac**:
**Username**: yancmhttps://gitlab.torproject.org/tpo/core/tor/-/issues/106INSTALL TOR WINDOWS XP2020-06-27T14:11:13ZTracINSTALL TOR WINDOWS XPAfter just install Tor 0.0.9.4.1, on msdos windows, this is the message I have :
Mar 03… (warn) Conn_read() :bug : unhandled error on read for Dir connection (fd 236) ; removing
Mar 03… (notice) conn_close_if_marked(): Conn (addr 18…. F...After just install Tor 0.0.9.4.1, on msdos windows, this is the message I have :
Mar 03… (warn) Conn_read() :bug : unhandled error on read for Dir connection (fd 236) ; removing
Mar 03… (notice) conn_close_if_marked(): Conn (addr 18…. Fd 236, type Dir, State 1) still wants to flush. Losing 66 bytes ! (Marked at c:\documents and settings_nick mathewson\my documents\src\tor\src\or\main.c:275)
I need some help ! Why doesn't it works. My PC is under WINDOWS XP SP2 with a firm firewall and proxy.
Sorry for my poor english, I'm from Paris (France).
thanks
Alyssa
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: alyssaNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/107Bandwidth reporting/bootstrapping2020-06-27T14:11:13ZTracBandwidth reporting/bootstrappingI've been running a Tor server (barf 0.0.9.5 Linux) for 3 weeks with very little usage. My reported bandwidth in the directory is pretty low, even if I have good connectivity (100 K/s). I have at most 1 or 2 connect attempt at the serve...I've been running a Tor server (barf 0.0.9.5 Linux) for 3 weeks with very little usage. My reported bandwidth in the directory is pretty low, even if I have good connectivity (100 K/s). I have at most 1 or 2 connect attempt at the server port (9001) per day. DirPort is set to 0, since I do not want to mirror the directory. Knowing that Tor client picks node that display sufficient bandwidth, it looks like the server need to be 'bootstrapped' initially by forcing some traffic through it, with another Tor client with a EntryNodes and StrictEntryNodes set. There are several 0.0.9.5 servers in the directory with such low bandwidth.
[Automatically added by flyspray2trac: Operating System: Other Linux]
**Trac**:
**Username**: qbarfhttps://gitlab.torproject.org/tpo/core/tor/-/issues/108No Tor server exists that allows exit2020-06-27T14:11:13ZTracNo Tor server exists that allows exitFeb 28 21:21:37.813 [notice] circuit_get_open_circ_or_launch(): No Tor
server exists that allows exit to 168.95.5.12:25. Rejecting.
Feb 28 21:21:38.208 [err] circuitlist.c:429: assert_cpath_layer_ok:
Assertion cp->deliver_window >= 0 fai...Feb 28 21:21:37.813 [notice] circuit_get_open_circ_or_launch(): No Tor
server exists that allows exit to 168.95.5.12:25. Rejecting.
Feb 28 21:21:38.208 [err] circuitlist.c:429: assert_cpath_layer_ok:
Assertion cp->deliver_window >= 0 failed; aborting.circuitlist.c:429 assert_cpath_layer_ok: Assertion cp->deliver_window
= 0 failed; aborting.
We are using Tor version 0.0.9.5. , compiled out of a source-tarball with no special compile-options
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: thomassNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/109assert_cpath_layer_ok(): Unexpected state 1712020-06-27T14:11:13ZTracassert_cpath_layer_ok(): Unexpected state 171Mar 02 01:37:03.412 [err] assert_cpath_layer_ok(): Unexpected state 171
Mar 02 01:37:03.412 [err] circuitlist.c:426: assert_cpath_layer_ok:
Assertion 0 failed; aborting.
circuitlist.c:426 assert_cpath_layer_ok: Assertion 0 failed; abort...Mar 02 01:37:03.412 [err] assert_cpath_layer_ok(): Unexpected state 171
Mar 02 01:37:03.412 [err] circuitlist.c:426: assert_cpath_layer_ok:
Assertion 0 failed; aborting.
circuitlist.c:426 assert_cpath_layer_ok: Assertion 0 failed; aborting.
Abort
We are using Tor version 0.0.9.5. , compiled out of a source-tarball with no special compile-options
[Automatically added by flyspray2trac: Operating System: All]
**Trac**:
**Username**: thomasshttps://gitlab.torproject.org/tpo/core/tor/-/issues/111sigpipes in 0.0.9.62020-06-27T14:11:13ZRoger Dingledinesigpipes in 0.0.9.6Mar 25 10:03:05.689 [info] connection_close_immediate(): fd 300, type Exit, state 3, 74 bytes on outbuf.
Mar 25 10:03:05.690 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
Mar 25 10:03:05.690 [info] connection_remove(): r...Mar 25 10:03:05.689 [info] connection_close_immediate(): fd 300, type Exit, state 3, 74 bytes on outbuf.
Mar 25 10:03:05.690 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
Mar 25 10:03:05.690 [info] connection_remove(): removing socket -1 (type Exit), nfds now 338
Mar 25 10:03:05.690 [notice] Caught sigpipe. Ignoring.
Mar 25 10:04:29.026 [info] connection_close_immediate(): fd 36, type Exit, state 3, 73 bytes on outbuf.
Mar 25 10:04:29.026 [info] conn_close_if_marked(): Cleaning up connection (fd -1).
Mar 25 10:04:29.026 [info] connection_remove(): removing socket -1 (type Exit), nfds now 312
Mar 25 10:04:29.027 [notice] Caught sigpipe. Ignoring.
[Automatically added by flyspray2trac: Operating System: All]0.0.9.7https://gitlab.torproject.org/tpo/core/tor/-/issues/112tor-resolve gives funny error message on failure2020-06-27T14:11:13ZRoger Dingledinetor-resolve gives funny error message on failure%tor-resolve imserver.com
Mar 28 22:17:44.706 [warn] parse_socks4a_resolve_response(): Got status response '91', meaning not success.
Mar 28 22:17:44.706 [err] do_resolve(): Error parsing SOCKS response
[Automatically added by flyspra...%tor-resolve imserver.com
Mar 28 22:17:44.706 [warn] parse_socks4a_resolve_response(): Got status response '91', meaning not success.
Mar 28 22:17:44.706 [err] do_resolve(): Error parsing SOCKS response
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/114hidden service descriptors quietly rejected when clock skewed2020-06-27T14:11:12ZRoger Dingledinehidden service descriptors quietly rejected when clock skewedMar 29 06:47:33.643 [warn] rend_cache_store(): Service descriptor h7dkd7zc7aeplgy4 is too far in the future
When clients publish hidden services but their clock is wrong, the hidden service doesn't work. There might
be a log entry expla...Mar 29 06:47:33.643 [warn] rend_cache_store(): Service descriptor h7dkd7zc7aeplgy4 is too far in the future
When clients publish hidden services but their clock is wrong, the hidden service doesn't work. There might
be a log entry explaining this, but perhaps the log entry doesn't say enough? In any case, a log entry may
not be enough to let the user know, if he never looks at his logs.
Is there a better way to communicate this to the user, or is there some way we can cope anyway? (E.g. be more
forgiving about clock skew wrt hidden service descriptors (easy) or remember our skew based on dirserver
timestamps and have Tor "fix" outgoing published timestamps (foolishly hard))
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/115win32 torrc file has funny line endings2020-06-27T14:11:12ZRoger Dingledinewin32 torrc file has funny line endingswordpad works for the win32 torrc we ship in 0.1.0.1-rc, but apparently notepad gets
confused by it. notepad apparently used to work for the previous ones.
is there something wrong with the torrc we ship, or did we skip a step in making...wordpad works for the win32 torrc we ship in 0.1.0.1-rc, but apparently notepad gets
confused by it. notepad apparently used to work for the previous ones.
is there something wrong with the torrc we ship, or did we skip a step in making the exe, or what?
[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]0.1.0.2-rcNick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/116OS X package UID is a login user2020-06-27T14:11:12ZTracOS X package UID is a login userIn the OS X installer, a user is created with a uid of 503 (the 500 range, anyway). UIDs in this range show up in the login window/fast user switching, which isn't right for the tor user.
UID=103 seems OK here, or perhaps sub 100? I hav...In the OS X installer, a user is created with a uid of 503 (the 500 range, anyway). UIDs in this range show up in the login window/fast user switching, which isn't right for the tor user.
UID=103 seems OK here, or perhaps sub 100? I haven't been able to track down any actual documentation on the ranges, will try to find some and update this.
[Automatically added by flyspray2trac: Operating System: OSX 10.4 Tiger]
**Trac**:
**Username**: matthttps://gitlab.torproject.org/tpo/core/tor/-/issues/117event poll failed: Invalid argument [22]2020-06-27T14:11:12Zgoodellevent poll failed: Invalid argument [22]Running 0.1.0.1-rc-cvs:
The Tor server summarily crashes within minutes of starting, with this error:
Mar 31 12:25:25.818 [err] do_main_loop(): event poll failed: Invalid argument [22]
[Automatically added by flyspray2trac: Operating...Running 0.1.0.1-rc-cvs:
The Tor server summarily crashes within minutes of starting, with this error:
Mar 31 12:25:25.818 [err] do_main_loop(): event poll failed: Invalid argument [22]
[Automatically added by flyspray2trac: Operating System: Other Linux]Nick MathewsonNick Mathewsonhttps://gitlab.torproject.org/tpo/core/tor/-/issues/118server crash when exiting2020-06-27T14:11:12ZRoger Dingledineserver crash when exitingMar 31 12:37:21.214 [notice] Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
Mar 31 12:37:21.347 [notice] Sigint received a second time; exiting now.
Segmentation fault
(gdb) where
#0 0x0808d11f in _openssl_lock...Mar 31 12:37:21.214 [notice] Interrupt: will shut down in 30 seconds. Interrupt again to exit now.
Mar 31 12:37:21.347 [notice] Sigint received a second time; exiting now.
Segmentation fault
(gdb) where
#0 0x0808d11f in _openssl_locking_cb (mode=9, n=9, file=0x40103857 "rsa_lib.c", line=217)
at crypto.c:1653
#1 0x4007b0b8 in CRYPTO_lock () from /lib/libcrypto.so.2
legacy/trac#2 0x4007b120 in CRYPTO_add_lock () from /lib/libcrypto.so.2
legacy/trac#3 0x4009e987 in RSA_free () from /lib/libcrypto.so.2
legacy/trac#4 0x08088f5d in crypto_free_pk_env (env=0x80d1cd0) at crypto.c:265
legacy/trac#5 0x08066663 in cpuworker_main (data=0x815f7f8) at cpuworker.c:272
legacy/trac#6 0x08086977 in tor_pthread_helper_fn (_data=0x8166278) at compat.c:685
legacy/trac#7 0x40122f77 in pthread_start_thread () from /lib/libpthread.so.0
legacy/trac#8 0x4020deba in thread_start () from /lib/libc.so.6
(gdb) print _openssl_mutexes[n]
Cannot access memory at address 0x24
(gdb) print n
$1 = 9
(gdb) print _openssl_mutexes
$2 = (tor_mutex_t **) 0x0
looks like we free the mutexes before we should?
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/119test bug, sorry for the noise2020-06-27T14:11:12Zweasel (Peter Palfrader)test bug, sorry for the noisehey there
</pre>
<a href="http://www.noreply.org">test</a></p>
<script language="JavaScript" type="text/javascript">
<!--
alert("WARNING: Turn off JavaScript _NOW_.");
// -->
</script>
[Automatically added by flyspray2trac: Operatin...hey there
</pre>
<a href="http://www.noreply.org">test</a></p>
<script language="JavaScript" type="text/javascript">
<!--
alert("WARNING: Turn off JavaScript _NOW_.");
// -->
</script>
[Automatically added by flyspray2trac: Operating System: All]https://gitlab.torproject.org/tpo/core/tor/-/issues/120servers don't transform destroys to truncateds2020-06-27T14:11:12ZRoger Dingledineservers don't transform destroys to truncatedsIn command_process_destroy_cell(), we are supposed to convert client-ward destroy cells into
truncated cells, so the client can know at what hop in the path the circuit broke. But we
don't actually do this currently, because the client b...In command_process_destroy_cell(), we are supposed to convert client-ward destroy cells into
truncated cells, so the client can know at what hop in the path the circuit broke. But we
don't actually do this currently, because the client behave was always to close the circuit,
so we were wasting bandwidth with a two-round-trip circuit close.
If we're going to start trying to re-extend circuits, though, we need this functionality.
Should we re-enable the ifdef 0'ed stuff (and remove the circuit_mark_for_close())?
[Automatically added by flyspray2trac: Operating System: All]