Setuid sandbox: exit(2) on SIGABRT

Setuid sandbox: exit(2) on SIGABRT

The setuid sandbox waits on its one child and then dies
afterwards.

When receiving SIGABRT, instead of dumping core, simply exit the
process. There is no interesting information to be gathered from
knowing that the process is inside waitid(2), one should look at
the child process instead.

This patch is in hope to reduce red herrings.

BUG=334345
TBR=jorgelo
NOTRY=true

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=251459

[jln (very slow on Chromium), 2014-02-14 21:29:17]

The CQ bit was checked by jln@chromium.org

[commit-bot: I haz the power, 2014-02-14 21:32:21]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/jln@chromium.org/167583002/10002

[jln (very slow on Chromium), 2014-02-15 00:42:11]

Committed patchset #2 manually as r251459 (presubmit successful).