BIND 10 #2942: b10-auth terminated with signal 6, Aborted.

[BIND 10 Development]

#2942: b10-auth  terminated with signal 6, Aborted.
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  very high     |                    Milestone:  New
           Component:  b10-auth      |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DNS           |              Defect Severity:  Very
Estimated Difficulty:  0             |  High
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:3 jreed]:
 > Replying to [comment:1 jreed]:
 > > #8  0x0000000801293119 in isc::asiodns::IOFetch::operator()
 (this=0x80321e918,
 > >     ec={value_ = 52554000, category_ = 8}, length=34413405056)
 > >     at io_fetch.cc:255

 This part of the backtrace doesn't make sense.  `AuthSrv`'s call back
 shouldn't be called from `IOFetch`.  Does it refer to the correct
 library?

 In either case, could we get at least one more backtrace?  The first
 backtrace also seems odd; it shows all threads are working as a
 data source client builder, which is impossible.

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