Add a Subzero variant of Chrome PNaCl error handling test.
Make sure that subzero can also handle various pexes with a
bad header. Test with a tiny fake .pexe (already had
that test case) and a larger realistic nonfinalized pexe.
The nonfinalized pexe requires streaming multiple chunks
and so is able to tickle an error-reporting race condition
(use-after-free) + possible deadlock. I tried it on subzero
from last week and was able to tickle the crash.
It should no longer tickle that bug this week unless
there's a regression.
The tiny version runs pretty quickly, but otherwise had
not been crashing before. It merely returned an imprecise
error message ("Some error occurred"), which should
now be fixed too.
BUG= https://code.google.com/p/nativeclient/issues/detail?id=4163
CQ_EXTRA_TRYBOTS=tryserver.chromium.linux:linux_chromium_dbg_32_ng
Review URL: https://codereview.chromium.org/
1157213005
Cr-Commit-Position: refs/heads/master@{#333769}