Fix Valgrind unittests by forcing illegal memory accesses to happen unconditi...

base/tools_sanity_unittest.cc

Index: base/tools_sanity_unittest.cc
===================================================================
--- base/tools_sanity_unittest.cc	(revision 62960)
+++ base/tools_sanity_unittest.cc	(working copy)
@@ -36,11 +36,13 @@
 }
 
 void ReadValueOutOfArrayBoundsLeft(char *ptr) {
-  VLOG(1) << "Reading a byte out of bounds: " << ptr[-2];
+  char c = ptr[-2];
+  VLOG(1) << "Reading a byte out of bounds: " << c;
 }
 
 void ReadValueOutOfArrayBoundsRight(char *ptr, size_t size) {
-  VLOG(1) << "Reading a byte out of bounds: " << ptr[size + 1];
+  char c = ptr[size + 1];
+  VLOG(1) << "Reading a byte out of bounds: " << c;
 }
 
 // This is harmless if you run it under Valgrind thanks to redzones.