Initialize yet another variable to silence GCC warning from last-but-one commit

Yet another BuildBot e-mail, yet another breakage on RHEL-7.1 s390x
(which uses an older GCC).  This time,
solib-svr4.c:solib_event_probe_action has the probe_argc variable,
which is now inside a TRY..CATCH and therefore needs to be
initialized.  Pushed as obvious.

gdb/ChangeLog:
2015-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* solib-svr4.c (solib_event_probe_action): Initialize 'probe_argc'
	as zero.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 80fff7e..b054438 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,10 @@
 2015-09-01  Sergio Durigan Junior  <sergiodj@redhat.com>
 
+       * solib-svr4.c (solib_event_probe_action): Initialize 'probe_argc'
+       as zero.
+
+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>

diff --git a/gdb/solib-svr4.c b/gdb/solib-svr4.c
index d3411fa..5d3d41e 100644 (file)
--- a/gdb/solib-svr4.c
+++ b/gdb/solib-svr4.c
@@ -1772,7 +1772,7 @@ static enum probe_action
 solib_event_probe_action (struct probe_and_action *pa)
 {
   enum probe_action action;
-  unsigned probe_argc;
+  unsigned probe_argc = 0;
   struct frame_info *frame = get_current_frame ();
 
   action = pa->action;