Re: [tor-bugs] #3367 [Tor Client]: Tor 0.2.3.x segfaults on SIGNAL TERM

["Tor Bug Tracker & Wiki" <torproject-admin@xxxxxxxxxxxxxx>]

#3367: Tor 0.2.3.x segfaults on SIGNAL TERM
------------------------+---------------------------------------------------
 Reporter:  rransom     |          Owner:  nickm             
     Type:  defect      |         Status:  needs_review      
 Priority:  major       |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------
Changes (by nickm):

  * status:  assigned => needs_review


Comment:

 Replying to [comment:3 rransom]:
 > Replying to [comment:2 nickm]:
 >
 > > Oho, here's the trouble; handle_control_signal is calling
 connection_handle_write directly, when it's a buf_t-only function!
 >
 > Perhaps `connection_handle_write` shouldn't be defined when bufferevents
 are enabled.

 Maybe.  The idea behind the current architecure is that you should be able
 to have bufferevents on only some connection types.  I did that to make it
 easier to debug.  At some point in the 0.2.3.x series, though, we should
 consider a switch.

 Anyways, have a look at branch bug3367 in my public repo.

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