Eventdns.c crash after closing and reopening ORPort
[Originally reported by Mike Gersten; moving here so I don't forget about it.]
See or-dev thread from September-October titled "Tor crash", especially: http://archives.seul.org/or/dev/Sep-2007/msg00031.html (initial post) http://archives.seul.org/or/dev/Sep-2007/msg00040.html (stack trace)
The circumstances were: "I first shut down the Or-port, to try to let all connections close. When it was time to actually say "Time to stop", I re-enabled the Or-port, and then sent a sigint. (If I send sigint without first re-enabling the or-port, Tor assumes that it should stop immediately, without notifying the clients).
Tor crashed about a minute later. I don't know if it was related or not.
This is 1.2.17."The stack trace was: 0 tor 0x00087c04 event_del + 44 (event.c:697) 1 tor 0x0006cdd4 nameserver_up + 84 (eventdns.c:533) 2 tor 0x0006cee0 reply_callback + 112 (eventdns.c:648) 3 tor 0x0006fc6c reply_handle + 684 (eventdns.c:740) 4 tor 0x000714cc nameserver_ready_callback + 1564 (eventdns.c:925) 5 tor 0x00087364 event_process_active + 240 (event.c:332) 6 tor 0x00087634 event_base_loop + 340 (event.c:448) 7 tor 0x000874cc event_loop + 40 (event.c:382) 8 tor 0x000873d0 event_dispatch + 20 (event.c:346) 9 tor 0x0004b8b0 tor_main + 656 (main.c:1270) 10 tor 0x0000277c _start + 760 11 tor 0x00002480 start + 48
[Automatically added by flyspray2trac: Operating System: All]