<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">In my synthetic test, I got the following behavior when attached to /bin/cat:<div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div># strace -p 2091</div></div><div><div>Process 2091 attached - interrupt to quit</div></div><div><div>read(0, 0x89e7000, 32768) = ? ERESTARTSYS (To be restarted)</div></div><div><div>--- SIGHUP (Hangup) @ 0 (0) ---</div></div><div><div>read(0, "", 32768) = 0</div></div><div><div>close(0) = 0</div></div><div><div>close(1) = 0</div></div><div><div>close(2) = -1 EBADF (Bad file descriptor)</div></div><div><div>exit_group(0) = ?</div></div><div><div>Process 2091 detached</div></div></blockquote><div><br></div><div>This seems like the desired behavior.</div><div><br></div><div>However, in the case where the WritableDatabase hung, I got the following behavior:</div><div><br></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div># strace -p 25694</div><div>Process 25694 attached - interrupt to quit</div><div>read(0, 0x859b000, 32768) = ? ERESTARTSYS (To be restarted)</div><div>--- SIGHUP (Hangup) @ 0 (0) ---</div><div>read(0, </div><div>^C <unfinished ...></div><div>Process 25694 detached</div></blockquote><div><br></div><div>Well, I'm not sure why there is a difference. Both processes were ignoring SIGHUP according to /proc/$pid/status</div><div><br></div><div>I'll keep on investigating.</div></body></html>