[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:  closed            
    Priority:  major         |   Milestone:  Tor: 0.2.3.x-final
   Component:  Tor Client    |     Version:                    
  Resolution:  fixed         |    Keywords:                    
      Parent:                |      Points:                    
Actualpoints:                |  
-----------------------------+----------------------------------------------
Changes (by mart.bakhoff):

  * status:  assigned => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:6 nickm]:
 > Sounds like a new bug to me.  I've merged bug3361.  The cache files and
 backtrace would probably be helpful.
 >
 > One more thing to check, though: Can you tell if the second bug occurs
 in git master?  I think we might have made some fixes around that code
 since 0.2.3.1-alpha came out.

 You were right! Latest git had microdesc_cache_rebuild fixed and your last
 commit fixed networkstatus_set_current_consensus. Everything seems to be
 working. Thanks!

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3361#comment:7>
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