BIND 10 #705: Log more helpful status when process exits under the boss

[BIND 10 Development]

#705: Log more helpful status when process exits under the boss
-------------------------------------+-------------------------------------
           Reporter:  shane          |                      Owner:
               Type:  enhancement    |                     Status:  new
           Priority:  minor          |                  Milestone:  feature
          Component:  Boss of BIND   |  backlog item
          Sensitive:  0              |                   Keywords:
Add Hours to Ticket:  0              |  Estimated Number of Hours:  0
        Total Hours:  0              |                  Billable?:  1
                                     |                  Internal?:  0
-------------------------------------+-------------------------------------
 Jeremy reported something exited with status 139.

 It turns out that the status value is as follows:

     a 16-bit number, whose low byte is the signal number that killed the
 process, and whose high byte is the exit status (if the signal number is
 zero); the high bit of the low byte is set if a core file was produced

 That is from the Python documentation here:

 http://docs.python.org/py3k/library/os.html#os.wait

 So, deciphering it we see that it is < 256, which means it is a signal.
 The high bit is set - meaning we have core. We can remove that by
 subtracting 128 and discover that this is signal 11 (SEGV).

 It would be nice if the boss process did this work and reported exactly
 what happened to the child process.

-- 
Ticket URL: <http://bind10.isc.org/ticket/705>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development