Fix bug 246 (occasional buffer overflow related to varargs in assertion-failure string construction) and addition of an assert_white unit test check for the issue

1 files changed, 25 insertions, 0 deletions

diff --git a/test/unit/util/assert_white.h b/test/unit/util/assert_white.h
index 389f2aa1b..75006ed12 100644
--- a/test/unit/util/assert_white.h
+++ b/test/unit/util/assert_white.h
@@ -71,6 +71,31 @@ public:
     } catch(...) {
       TS_FAIL("Threw the wrong kind of exception !");
     }
+
+    // Now test an assert with a format that drives it over the 512
+    // byte initial buffer.  This was a bug in r1441, see bug 246:
+    // http://goedel.cims.nyu.edu/bugzilla3/show_bug.cgi?id=246
+    string fmt = string(200, 'x') + " %s " + string(200, 'x');
+    string arg(200, 'y');
+    try {
+      AlwaysAssert(false, fmt.c_str(), arg.c_str());
+      TS_FAIL("Should have thrown an exception !");
+    } catch(AssertionException& e) {
+      // we don't want to match on the entire string, because it may
+      // have an absolute path to the unit test binary, line number
+      // info, etc.
+      const char* theString = e.toString().c_str();
+      const char* firstPart =
+        "Assertion failure\nvoid AssertWhite::testReallyLongAssert()\n";
+      string lastPartStr = "\n\n  false\n" + string(200, 'x') + " " +
+        string(200, 'y') + " " + string(200, 'x');
+      const char* lastPart = lastPartStr.c_str();
+      TS_ASSERT(strncmp(theString, firstPart, strlen(firstPart)) == 0);
+      TS_ASSERT(strncmp(theString + strlen(theString) - strlen(lastPart),
+                        lastPart, strlen(lastPart)) == 0);
+    } catch(...) {
+      TS_FAIL("Threw the wrong kind of exception !");
+    }
   }
 
   void testUnreachable() {