[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #3361 [Tor Client]: tor-0.2.3.1 segfault in networkstatus_set_current_consensus

#3361: tor-0.2.3.1 segfault in networkstatus_set_current_consensus
--------------------------+-------------------------------------------------
 Reporter:  mart.bakhoff  |          Owner:  nickm             
     Type:  defect        |         Status:  assigned          
 Priority:  major         |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client    |        Version:                    
 Keywords:                |         Parent:                    
   Points:                |   Actualpoints:                    
--------------------------+-------------------------------------------------
Changes (by nickm):

  * priority:  normal => major
  * owner:  => nickm
  * status:  new => assigned
  * milestone:  => Tor: 0.2.3.x-final


Comment:

 Looks like the current_consensus result is NULL in
 {{{
   if (now < current_consensus->valid_after - EARLY_CONSENSUS_NOTICE_SKEW)
 {
 }}}
 This happens because the consensus we just set wasn't the one we were
 going to use.  Options seem to be checking whichever consensus we just
 got, or checking the result for NULL.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3361#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs