From: Sergio Durigan Junior Date: Wed, 2 Sep 2015 04:34:22 +0000 (-0400) Subject: Initialize variable and silence GCC warning from last commit X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=ad1c917a79e8c5aa67657f148415c1bee01b240f;p=binutils-gdb.git Initialize variable and silence GCC warning from last commit 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 * solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL --- diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 8ed469f5df6..80fff7e41d9 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,7 @@ +2015-09-01 Sergio Durigan Junior + + * solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL + 2015-09-01 Sergio Durigan Junior * solib-svr4.c (solib_event_probe_action): Call diff --git a/gdb/solib-svr4.c b/gdb/solib-svr4.c index 5d2b9dde218..d3411faf831 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 ();