Custom Query (25152 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (73 - 75 of 25152)

Ticket Resolution Summary Owner Reporter
#160 Works for me "GETINFO network-status" seems to fail rm
Description

When I send a GETINFO control message with the parameter "network-status", the server seems to close the control connection. The timing appears to be inconsistent, sometimes the reply message can be read fully, after which the socket is closed, sometimes only 8636 bytes can be read. (The number may be coincidental, but was constant in my tests.) Found in 0.1.0.9-rc on win32.

agl ran the demo python script on 0.1.1.0-alpha-cvs and received the following output:

... [12:41] <agl> {'version': '0.1.1.0-alpha-cvs'} [12:41] <agl> Traceback (most recent call last): [12:41] <agl> File "TorControl.py", line 457, in ? [12:41] <agl> do_main_loop(sh,sp) [12:41] <agl> File "TorControl.py", line 425, in do_main_loop [12:41] <agl> print get_info(s,"network-status") [12:41] <agl> File "TorControl.py", line 305, in get_info [12:41] <agl> tp,body = receive_reply(s,[MSG_TYPE.INFOVALUE]) [12:41] <agl> File "TorControl.py", line 247, in receive_reply [12:41] <agl> raise ErrorReply((errCode, [12:41] <agl> main.ErrorReply: (1, 'Internal error', 'network-status')

[Automatically added by flyspray2trac: Operating System: All]

#161 Fixed Tor links to pthreads on OpenBSD by default jon
Description

The ChangeLog and configure.in state that threads are disabled on OpenBSD and NetBSD by default, but it still continues to link to them when building.

uname -a

OpenBSD chaos.brain-box.net 3.7 FLOW#40 i386

gcc -g -O2 -Wall -g -O2 -o tor buffers.o circuitbuild.o circuitlist.o circuituse.o command.o config.o connection.o connection_edge.o connection_or.o control.o cpuworker.o directory.o dirserv.o dns.o hibernate.o main.o onion.o relay.o rendcommon.o rendclient.o rendmid.o rendservice.o rephist.o router.o routerlist.o routerparse.o tor_main.o ../common/libor.a ../common/libor-crypto.a -lz -lssl -lcrypto -lpthread -levent ../common/libor.a(util.o)(.text+0x3bf): In function `tor_strpartition': /home/jon/src/tor-0.1.0.10/src/common/util.c:265: warning: strcpy() is almost always misused, please use strlcpy() ../common/libor.a(util.o)(.text+0xad9): In function `base16_encode': /home/jon/src/tor-0.1.0.10/src/common/util.c:466: warning: sprintf() is often misused, please use snprintf() gcc -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -Wall -g -O2 -c test.c gcc -g -O2 -Wall -g -O2 -o test buffers.o circuitbuild.o circuitlist.o circuituse.o command.o config.o connection.o connection_edge.o connection_or.o control.o cpuworker.o directory.o dirserv.o dns.o hibernate.o main.o onion.o relay.o rendcommon.o rendclient.o rendmid.o rendservice.o rephist.o router.o routerlist.o routerparse.o test.o ../common/libor.a ../common/libor-crypto.a -lz -lssl -lcrypto -lpthread -levent test.o(.text+0x2077): In function `test_crypto': /home/jon/src/tor-0.1.0.10/src/or/test.c:490: warning: strcpy() is almost always misused, please use strlcpy() ../common/libor.a(util.o)(.text+0xad9): In function `base16_encode': /home/jon/src/tor-0.1.0.10/src/common/util.c:466: warning: sprintf() is often misused, please use snprintf() test.o(.text+0x23c1): In function `test_crypto': /home/jon/src/tor-0.1.0.10/src/or/test.c:531: warning: strcat() is almost always misused, please use strlcat() Making all in tools cd ../.. && CONFIG_FILES=src/tools/Makefile CONFIG_HEADERS= /bin/sh ./config.status config.status: creating src/tools/Makefile config.status: executing default-1 commands gcc -DHAVE_CONFIG_H -I. -I. -I../.. -g -O2 -Wall -g -O2 -c tor-resolve.c gcc -g -O2 -Wall -g -O2 -o tor-resolve tor-resolve.o ../common/libor.a -lpthread -levent tor-resolve.o(.text+0x89): In function `build_socks4a_resolve_request': *

Even specifing --disable-threads to ./configure does not fix the problem. It still links to pthreads. 'ldd' verifies this :

ldd tor

tor:

Start End Type Ref Name 00000000 00000000 exe 1 tor 0eb93000 2eb9b000 rlib 1 /usr/lib/libz.so.4.0 09bd2000 29bdd000 rlib 1 /usr/lib/libssl.so.10.0 08447000 28475000 rlib 1 /usr/lib/libcrypto.so.12.0 0ae21000 2ae2a000 rlib 1 /usr/lib/libpthread.so.6.1 0809d000 280d6000 rlib 1 /usr/lib/libc.so.38.0 0890b000 0890b000 rtld 1 /usr/libexec/ld.so

[Automatically added by flyspray2trac: Operating System: BSD]

#162 Fixed "The service did not return an error." message bknobbs
Description

Get "The service did not return an error." message when trying to stop service in services.msc in windows (on windows XP SP2). It does close the process, and if you try and tell it to stop again, it just hangs for a while, and eventually says that it stopped. After this you can hit start process, and everything works normally.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Note: See TracQuery for help on using queries.