i#1734: Create Dr. Fuzz: adjust MAX_BUFFER_SIZE to 64MB

Commit log for first patchset:
---------------
i#1734: Create Dr. Fuzz: adjust MAX_BUFFER_SIZE to 64MB

- set MAX_BUFFER_SIZE to 64MB to allow large input
---------------

[bruening, 2015-10-28 22:18:02]

LGTM w/ suggestions

https://codereview.appspot.com/272250043/diff/1/drmemory/fuzzer.c
File drmemory/fuzzer.c (right):

https://codereview.appspot.com/272250043/diff/1/drmemory/fuzzer.c#newcode537
drmemory/fuzzer.c:537: #define MAX_BUFFER_SIZE (64*1024*1024) /* 64MB */
I think this should result in a warning, not a fatal error, and as such the name
should be sthg like MAX_EXPECTED_BUFFER_SIZE

https://codereview.appspot.com/272250043/diff/1/drmemory/fuzzer.c#newcode723
drmemory/fuzzer.c:723: ASSERT(false, "Target's buffer size too large");
Suggest: this should be a warning not a fatal error b/c user may want a huge
buffer

[bruening, 2015-10-28 22:18:27]

https://codereview.appspot.com/272250043/diff/1/drmemory/fuzzer.c
File drmemory/fuzzer.c (right):

https://codereview.appspot.com/272250043/diff/1/drmemory/fuzzer.c#newcode537
drmemory/fuzzer.c:537: #define MAX_BUFFER_SIZE (64*1024*1024) /* 64MB */
On 2015/10/28 22:18:02, bruening wrote:
> I think this should result in a warning, not a fatal error, and as such the
name
> should be sthg like MAX_EXPECTED_BUFFER_SIZE

If this stays a fatal error, this size should be documented in user-facing docs

[zhaoqin, 2015-10-28 22:33:53]

Committed as
https://github.com/DynamoRIO/drmemory/commit/f6d1588d542b8cd20f78ab4c5321a5ac...

Final commit log: 
---------------
i#1734: Create Dr. Fuzz: adjust MAX_BUFFER_SIZE to 64MB

- set MAX_BUFFER_SIZE to 64MB to allow large input
- use WARN instead of fatal error on large buffer

Review-URL: https://codereview.appspot.com/272250043
---------------