Print additional message for RELEASE_ASSERT in builds used for fuzzing.

third_party/WebKit/Source/wtf/text/StringConcatenate.h

Index: third_party/WebKit/Source/wtf/text/StringConcatenate.h
diff --git a/third_party/WebKit/Source/wtf/text/StringConcatenate.h b/third_party/WebKit/Source/wtf/text/StringConcatenate.h
index 63a7c4e296292295007d7a15bff37fa10dac4e9e..b9c6d948a08e6e23d2ef7e9f5f4fb1e90adab565 100644
--- a/third_party/WebKit/Source/wtf/text/StringConcatenate.h
+++ b/third_party/WebKit/Source/wtf/text/StringConcatenate.h
@@ -171,7 +171,7 @@ public:
 
     bool is8Bit() { return false; }
 
-    NO_RETURN_DUE_TO_CRASH void writeTo(LChar*)
+    void writeTo(LChar*)

[mmoroz, 2016/08/25 10:45:53]

Another approach could be:

    NO_RETURN_DUE_TO_CRASH void writeTo(LChar*)
    {
        RELEASE_ASSERT(false);
        CRASH();
    }


Otherwise, the compiler doesn't believe that this function is 'noreturn' and
gives a warning (i.e. error):

../../third_party/WebKit/Source/wtf/text/StringConcatenate.h:177:5: error:
function declared 'noreturn' should not return [-Werror,-Winvalid-noreturn]
    }
    ^
1 error generated.

[tkent, 2016/08/25 12:54:06]

IMO, it's ok to remove NO_RETURN_DE_TO_CRASH here.
NO_RETURN_DE_TO_CRASH doesn't have much benefit, and I'd like to remove
NO_RETURN_DE_TO_CRASH itself.

     {
         RELEASE_ASSERT(false);
     }