Add check for Linux minidump ending on bad write for exploitability rating.

src/processor/exploitability_linux.h

 // Copyright (c) 2013 Google Inc.
 // All rights reserved.
 //
 // Redistribution and use in source and binary forms, with or without
 // modification, are permitted provided that the following conditions are
 // met:
 //
 //     * Redistributions of source code must retain the above copyright
 // notice, this list of conditions and the following disclaimer.
 //     * Redistributions in binary form must reproduce the above
@@ skipping 40 matching lines @@
   virtual ExploitabilityRating CheckPlatformExploitability();
 
  private:
   // This method takes the address of the instruction pointer and returns
   // whether the instruction pointer lies in a valid instruction region.
   bool InstructionPointerInCode(uint64_t instruction_ptr);
 
   // This method checks the exception that triggered the creation of the
   // minidump and reports whether the exception suggests no exploitability.
   bool BenignCrashTrigger(const MDRawExceptionStream *raw_exception_stream);
+
+  // This method checks if the crash occurred during a write to read-only

[ahonig, 2015/08/10 22:53:11]

nit, read-only or completely invalid memory right?

[liuandrew, 2015/08/17 21:37:36]

Done.

Yes, both read-only and invalid.

+  // memory. It does so by checking if the instruction at the instruction
+  // pointer is a write instruction, and if the target of the instruction
+  // is at a spot in memory that prohibits writes.
+  bool EndedOnIllegalWrite(uint64_t instruction_ptr);
 };
 
 }  // namespace google_breakpad
 
 #endif  // GOOGLE_BREAKPAD_PROCESSOR_EXPLOITABILITY_LINUX_H_