commit 9a7ce9fbef026610c86af15c76af2d8b92654412
author Mike Frysinger <vapier@chromium.org> Sat Jan 19 11:03:37 2013 -0500
committer ChromeBot <chrome-bot@google.com> Fri Feb 15 10:40:02 2013 -0800
tree 4fc06f832c150e0ca8f4f862555b80067d59ad55
parent 570dd0ccae1ca812e3cd1289c414158f2cab9dda

use volatile markings in crash test

This makes it work with clang (supposedly).

BUG=chromium-os:37965
TEST=`cros_run_unit_tests --board=stumpy -p crash-reporter` passes

Change-Id: I598df1be7c8a38e14cde5f5328a3b6e2e1532ea7
Reviewed-on: https://gerrit.chromium.org/gerrit/43377
Reviewed-by: Ben Chan <benchan@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>

crash_reporter/crash_reporter.cc

diff --git a/crash_reporter/crash_reporter.cc b/crash_reporter/crash_reporter.cc
index de67326..401448e 100644
--- a/crash_reporter/crash_reporter.cc
+++ b/crash_reporter/crash_reporter.cc
@@ -148,7 +148,7 @@
   // Make it possible to test what happens when we crash while
   // handling a crash.
   if (FLAGS_crash_test) {
-    *(char *)0 = 0;
+    *(volatile char *)0 = 0;
     return 0;
   }