summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2022-04-07 10:17:02 -0600
committerTom Tromey <tromey@adacore.com>2022-04-14 10:19:16 -0600
commitdb7127461e1598b9a86ab2c2a365ea0c28d38817 (patch)
tree422ec4f2590f8a47789c2cf47350d6a86c83104e
parent7b5e70a921a6c168459002e7a3a464791ae75cc2 (diff)
downloadbinutils-gdb-db7127461e1598b9a86ab2c2a365ea0c28d38817.tar.gz
Silence -Wmaybe-uninitialized warning from target_waitstatus
Currently, one use of target_waitstatus yields a warning: target/waitstatus.h: In function 'void stop_all_threads()': target/waitstatus.h:175:13: warning: 'ws.target_waitstatus::m_value' may be used uninitialized in this function [-Wmaybe-uninitialized] 175 | m_value = other.m_value; | ~~~~~~~~^~~~~~~~~~~~~~~ This patch silences the warning. I tried the "volatile member" approach that was used for gdb::optional, but that didn't work, so this patch simply initializes the member.
-rw-r--r--gdb/target/waitstatus.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/target/waitstatus.h b/gdb/target/waitstatus.h
index 7b5faed83c7..63bbd737749 100644
--- a/gdb/target/waitstatus.h
+++ b/gdb/target/waitstatus.h
@@ -418,7 +418,7 @@ private:
char *execd_pathname;
/* Syscall number */
int syscall_number;
- } m_value;
+ } m_value {};
};
/* Extended reasons that can explain why a target/thread stopped for a