This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH] Initialize variable and silence GCC warning from last commit
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: GDB Patches <gdb-patches at sourceware dot org>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>
- Date: Wed, 2 Sep 2015 00:37:58 -0400
- Subject: [PATCH] Initialize variable and silence GCC warning from last commit
- Authentication-results: sourceware.org; auth=none
- References: <87pp215u3f dot fsf at redhat dot com>
BuildBot e-mailed me to let me know that my last commit broke GDB on
RHEL-7.1 s390x. On solib-svr4.c:svr4_handle_solib_event, 'val' now
needs to be initialized as NULL because it is inside a TRY..CATCH
block. This patch does that. Pushed as obvious.
gdb/ChangeLog:
2015-09-01 Sergio Durigan Junior <sergiodj@redhat.com>
* solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL
---
gdb/ChangeLog | 4 ++++
gdb/solib-svr4.c | 2 +-
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 8ed469f..80fff7e 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,9 @@
2015-09-01 Sergio Durigan Junior <sergiodj@redhat.com>
+ * solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL
+
+2015-09-01 Sergio Durigan Junior <sergiodj@redhat.com>
+
* solib-svr4.c (solib_event_probe_action): Call
get_probe_argument_count using TRY...CATCH.
(svr4_handle_solib_event): Likewise, for evaluate_probe_argument.
diff --git a/gdb/solib-svr4.c b/gdb/solib-svr4.c
index 5d2b9dd..d3411fa 100644
--- a/gdb/solib-svr4.c
+++ b/gdb/solib-svr4.c
@@ -1908,7 +1908,7 @@ svr4_handle_solib_event (void)
struct probe_and_action *pa;
enum probe_action action;
struct cleanup *old_chain, *usm_chain;
- struct value *val;
+ struct value *val = NULL;
CORE_ADDR pc, debug_base, lm = 0;
int is_initial_ns;
struct frame_info *frame = get_current_frame ();
--
2.4.3