Opened 10 years ago

Last modified 8 years ago

#1341 closed defect (Fixed)

Tor segfaults on hup

Reported by: Sebastian Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Sebastian, ilter, arma, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


A Tor configured as a client in a private network segfaulted on hup.
This is reproducible for me always. libevent version is


0 libevent.3.dylib 0x00000001001b8874 evdns_base_clear_nameservers_and_suspend + 20 (evdns.c:2247)
1 tor 0x000000010005dcc1 dns_reset + 33
2 tor 0x00000001000213c1 options_act + 1361
3 tor 0x0000000100022142 set_options + 498
4 tor 0x000000010002283e options_init_from_string + 494
5 tor 0x0000000100022cc8 options_init_from_torrc + 808
6 tor 0x0000000100068569 signal_callback + 953
7 libevent.3.dylib 0x000000010019ef34 event_base_loop + 1860 (event.c:944)
8 tor 0x000000010006a91f do_main_loop + 415
9 tor 0x000000010006ab4e tor_main + 78
10 tor 0x00000001000012b4 start + 52

(Fix coming soon)

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (5)

comment:1 Changed 10 years ago by Sebastian

So it is not only in private networks, the bug happens on any client (not
bridges, relays though).

Proposed fix in branch bug1341 in my repo.

comment:2 Changed 10 years ago by Sebastian

Ah, the reason why nobody has reported this is because it only happens
with libevent 2.x. Maybe that means Major -> Minor importance?

comment:3 Changed 10 years ago by arma

Fixed in

comment:4 Changed 10 years ago by arma

flyspray2trac: bug closed.

comment:5 Changed 8 years ago by nickm

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