Tolerate weird cl_kernels modules on Mac OS X 10.11

snapshot/mac/process_reader_test.cc

 // Copyright 2014 The Crashpad Authors. All rights reserved.
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
 // You may obtain a copy of the License at
 //
 //     http://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
@@ skipping 514 matching lines @@
   process_reader_threaded_child.Run();
 }
 
 TEST(ProcessReader, ChildSeveralThreads) {
   const size_t kChildThreads = 64;
   ProcessReaderThreadedChild process_reader_threaded_child(kChildThreads);
   process_reader_threaded_child.Run();
 }
 
 // cl_kernels images (OpenCL kernels) are weird. They’re not ld output and don’t
-// exist as files on disk. On Mac OS X 10.10, their Mach-O structure isn’t
+// exist as files on disk. On OS X 10.10 and 10.11, their Mach-O structure isn’t
 // perfect. They show up loaded into many executables, so these quirks should be
 // tolerated.
 //
 // Create an object of this class to ensure that at least one cl_kernels image
 // is present in a process, to be able to test that all of the process-reading
 // machinery tolerates them. On systems where cl_kernels modules have known
 // quirks, the image that an object of this class produces will also have those
 // quirks.
 //
 // https://openradar.appspot.com/20239912
@@ skipping 283 matching lines @@
   ScopedOpenCLNoOpKernel ensure_cl_kernels;
   ASSERT_NO_FATAL_FAILURE(ensure_cl_kernels.SetUp());
 
   ProcessReaderModulesChild process_reader_modules_child;
   process_reader_modules_child.Run();
 }
 
 }  // namespace
 }  // namespace test
 }  // namespace crashpad