From d636675137d7d7d81a7317dbd3a3bccacf367818 Mon Sep 17 00:00:00 2001
From: Willy Tarreau <w@1wt.eu>
Date: Thu, 25 Apr 2019 08:55:47 +0200
Subject: [PATCH] BUG/MINOR: activity: always initialize the profiling variable

It happens it was only set if present in the configuration. It's
harmless anyway but can still cause doubts when comparing logs and
configurations so better correctly initialize it.

This should be backported to 1.9.
---
 src/activity.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/activity.c b/src/activity.c
index b5fac8841..b48f4b43b 100644
--- a/src/activity.c
+++ b/src/activity.c
@@ -23,7 +23,7 @@
 
 
 /* bit field of profiling options. Beware, may be modified at runtime! */
-unsigned int profiling;
+unsigned int profiling = 0;
 
 /* One struct per thread containing all collected measurements */
 struct activity activity[MAX_THREADS] __attribute__((aligned(64))) = { };