commit 1597628fa38d24f23ad505bfb40e70e7c8617457
author caryclark <caryclark@google.com> Thu Jul 21 05:48:43 2016 -0700
committer Commit bot <commit-bot@chromium.org> Thu Jul 21 05:48:44 2016 -0700
tree 1404694d03aa87c0d78d73701b710f4ab880f4bc
parent ec336deffbf5945f2249f822b1ccc4628a9906a4

fix fuzzer bug

Fix another fuzzer bug.

Some PathOps asserts only make sense if the incoming data is
well-behaved. Well-behaved tests set debugging state to
trigger these additional asserts.

Formalize this by creating macros similar to SkASSERT that
check to see if the assert should be skipped.

TBR=reed@google.com
BUG=629962
GOLD_TRYBOT_URL= https://gold.skia.org/search?issue=2169863002

Review-Url: https://codereview.chromium.org/2169863002

src/pathops/SkOpSegment.h

diff --git a/src/pathops/SkOpSegment.h b/src/pathops/SkOpSegment.h
index 55e67a5d..7cf4b26 100644
--- a/src/pathops/SkOpSegment.h
+++ b/src/pathops/SkOpSegment.h
@@ -186,7 +186,7 @@
     double distSq(double t, const SkOpAngle* opp) const;
 
     bool done() const {
-        SkASSERT(this->globalState()->debugSkipAssert() || fDoneCount <= fCount);
+        SkOPASSERT(fDoneCount <= fCount);
         return fDoneCount == fCount;
     }