Opened 15 years ago

Last modified 7 years ago

#102 closed defect (Fixed)

CVS current crashes immediately on launch

Reported by: yancm Owned by:
Priority: Very High Milestone:
Component: Core Tor/Tor Version: 0.1.0.0-alpha-cvs
Severity: Keywords:
Cc: yancm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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
#2 0x0805be68 in assert_connection_ok (conn=0x8122700, now=1109262703)

at connection.c:1649

#3 0x0806ba05 in conn_read_callback (fd=23, event=2, _conn=0x8122700)

at main.c:339

#4 0x481e8a8c in event_process_active () from /usr/lib/libevent.so.0
#5 0x481e8c35 in event_loop () from /usr/lib/libevent.so.0
#6 0x481e8ab6 in event_dispatch () from /usr/lib/libevent.so.0
#7 0x0806c915 in do_main_loop () at main.c:1027
#8 0x0806d2c5 in tor_main (argc=1, argv=0xbfbffb80) at main.c:1656
#9 0x0807d04f in main (argc=1, argv=0xbfbffb80) at tor_main.c:18
#10 0x0804baf2 in _start ()

I'm running on netbsd 2.0_stable, P2-300 with 256M ram.

[Automatically added by flyspray2trac: Operating System: Other]

Child Tickets

Change History (4)

comment:1 Changed 15 years ago by nickm

Thanks for the backtrace! I think the patch I just committed should fix this. Can you confirm?

comment:2 Changed 15 years ago by yancm

Yes, my build with this patch is running now. I've been up a couple of minutes which beats crash on launch!

I was hoping I wasn't being hypersensitive to CVS builds...that's real-time response! Thanks!

comment:3 Changed 15 years ago by nickm

flyspray2trac: bug closed.

comment:4 Changed 7 years ago by nickm

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