BIND 10 #146: xfrout exception

[BIND 10 Development]

#146: xfrout exception
--------------------+-------------------------------------------------------
 Reporter:  jreed   |        Owner:  jreed                                         
     Type:  defect  |       Status:  assigned                                      
 Priority:  major   |    Milestone:  05. 3rd Incremental Release: Serious Secondary
Component:  xfrout  |   Resolution:                                                
 Keywords:          |    Sensitive:  0                                             
--------------------+-------------------------------------------------------

Comment(by shane):

 I asked Jelte to review in Jabber:

 {{{
 (13:59:56) jelte: just a question, does the signal not get trapped by
 this?
 (13:59:57) shane: Which I actually use quite often to do exception
 filtering, like you see there.
 (14:00:23) shane: The problem is that the signal is causing the select()
 call to return EINTR, regardless of how it is handled.
 (14:01:14) shane: So, if the SIGINT handler sets a flag which gets checked
 in a safe spot of the code, the select() still gets EINTR returned.
 (14:01:19) shane: Which causes an exception.
 (14:01:26) jelte: yeah i understand that, and i can't reproduce here
 anyway, it's just that i'm wondering if the signal doesn't get dropped in
 that case now
 (14:01:28) shane: I had the same problem in the boss program.
 (14:02:00) jelte: something similar is also present in startup code of
 other parts, though i don't really see that as a problem
 (14:02:03) shane: I don't know... I don't think it gets dropped.
 (14:02:35) jelte: in that case patch seem fine to me
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/146#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development