linux-fs: zero packet buffer initially

This fixes Valgrind warnings.

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

diff --git a/platforms/linux-fs/barectf-platform-linux-fs.c b/platforms/linux-fs/barectf-platform-linux-fs.c
index f2b3b9b757f69edd862a57971d6c2a77fcd59600..d91b474fb31d60fd30bf9f7aa1a0359f053eedaf 100644 (file)
--- a/platforms/linux-fs/barectf-platform-linux-fs.c
+++ b/platforms/linux-fs/barectf-platform-linux-fs.c
@@ -26,6 +26,7 @@
 #include <stdio.h>
 #include <stdlib.h>
 #include <stdint.h>
+#include <string.h>
 #include <assert.h>
 #include <barectf.h>
 #include <time.h>
@@ -115,6 +116,8 @@ struct barectf_platform_linux_fs_ctx *barectf_platform_linux_fs_init(
                return NULL;
        }
 
+       memset(buf, 0, buf_size);
+
        sprintf(stream_path, "%s/stream", trace_dir);
        ctx->fh = fopen(stream_path, "wb");