Revert "Fix locking for printing error messages."

Revert "Fix locking for printing error messages."

This reverts commit 187b3dfab5cca45e2af192bf7f5db09bcc156314.

A unit test fails when it shouldn't.

BUG= https://code.google.com/p/nativeclient/issues/detail?id=4138

Committed: https://gerrit.chromium.org/gerrit/gitweb?p=native_client/pnacl-subzero.git;a=commit;h=85f1ffe2a98e4402cab7c3c00a752ea42197fa7b

[Karl, 2015-04-16 22:11:11]

Committed patchset #1 (id:1) manually as
85f1ffe2a98e4402cab7c3c00a752ea42197fa7b (presubmit successful).

[Karl, 2015-04-16 22:12:46]

kschimpf@google.com changed reviewers:
+ jvoung@chromium.org

[jvoung (off chromium), 2015-04-16 22:25:42]

lgtm

I didn't see an error, but I did see a warning:

[WARNING]
../toolchain_build/src/llvm/utils/unittest/googletest/src/gtest-death-test.cc:791::
Death tests use fork(), which is unsafe particularly in a threaded context. For
this test, Google Test couldn't detect the number of threads.

[Karl, 2015-04-16 22:27:33]

In my version of master, I'm now getting a core dump inside ErrorAt. I couldn't
figure out why this didn't start happening until after I was working on another
CL (it worked many times before failing).

Hence, to be safe, I backed it out until I could figure out what was wrong.

[Karl, 2015-04-16 22:47:13]

Relanding as https://codereview.chromium.org/1097563003.

Problem appears to be corrupt LLVM compile.