IPC fuzzer: create message_lib library.

tools/ipc_fuzzer/message_lib/message_file_format.h

Index: tools/ipc_fuzzer/message_lib/message_file_format.h
diff --git a/tools/ipc_fuzzer/message_lib/message_file_format.h b/tools/ipc_fuzzer/message_lib/message_file_format.h
new file mode 100644
index 0000000000000000000000000000000000000000..31dbd71f7281583f8da6cb20b367504544942716
--- /dev/null
+++ b/tools/ipc_fuzzer/message_lib/message_file_format.h
@@ -0,0 +1,24 @@
+// Copyright 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef TOOLS_IPC_FUZZER_MESSAGE_LIB_MESSAGE_FILE_FORMAT_H_
+#define TOOLS_IPC_FUZZER_MESSAGE_LIB_MESSAGE_FILE_FORMAT_H_
+
+#include "base/basictypes.h"
+

[Tom Sepez, 2013/12/06 18:57:16]

You'll want a comment here describing the format of this file.  ASCII art?

[aedla, 2013/12/09 18:08:32]

Done.

+namespace ipc_fuzzer {
+
+struct FileHeader {
+  uint32 message_count;

[Tom Sepez, 2013/12/06 18:57:16]

I'd suggests having a magic number here just to be sure what you're opening is a
message file.

[aedla, 2013/12/09 18:08:32]

Added magic and version.

+  uint32 name_count;
+};

[Tom Sepez, 2013/12/06 18:57:16]

Hard to detect corruption if the counts are wrong ...

[aedla, 2013/12/09 18:08:32]

I think it's unlikely that the magic is correct and counts are wrong. If it
happens, I would think that further parsing will likely fail.

+
+struct NameTableEntry {
+  uint32 type;
+  uint32 string_table_offset;
+};
+
+}  // namespace ipc_fuzzer
+
+#endif  // TOOLS_IPC_FUZZER_MESSAGE_LIB_MESSAGE_FILE_FORMAT_H_