sandbox: fix DeathMessage tests in official builds

sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507
Committed: https://crrev.com/c13ff44abef008d4117b54d01ebf4912275c5fc6
Cr-Commit-Position: refs/heads/master@{#394867}

[mdempsky, 2016-05-19 20:08:24]

mdempsky@chromium.org changed reviewers:
+ jln@chromium.org, rickyz@chromium.org

[mdempsky, 2016-05-19 20:08:24]

jln/rickyz: PTAL

krasin/ihf/tfiga: FYI. I tested that this passes using krasin's repro steps from
crbug.com/612507 at least.

[krasin, 2016-05-19 20:35:57]

LGTM

[mdempsky, 2016-05-19 20:43:14]

Description was changed from

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

BUG=612507
==========

to

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507
==========

[mdempsky, 2016-05-19 20:43:18]

The CQ bit was checked by mdempsky@chromium.org

[commit-bot: I haz the power, 2016-05-19 20:43:53]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1994303002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1994303002/1

[commit-bot: I haz the power, 2016-05-19 21:17:52]

Description was changed from

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507
==========

to

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507
==========

[commit-bot: I haz the power, 2016-05-19 21:17:53]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 21:19:09]

Description was changed from

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507
==========

to

==========
sandbox: fix DeathMessage tests in official builds

It seems that official builds now use the "ud2" instruction to handle
CHECK failures, which causes the process to exit due to SIGILL instead
of SIGABRT. Unclear at the moment exactly why (maybe a toolchain
change?), but easy to workaround for now.

TBR=jln@chromium.org
BUG=612507

Committed: https://crrev.com/c13ff44abef008d4117b54d01ebf4912275c5fc6
Cr-Commit-Position: refs/heads/master@{#394867}
==========

[commit-bot: I haz the power, 2016-05-19 21:19:10]

Patchset 1 (id:??) landed as
https://crrev.com/c13ff44abef008d4117b54d01ebf4912275c5fc6
Cr-Commit-Position: refs/heads/master@{#394867}