Initialize yet another variable to silence GCC warning from last-but-one commit
authorSergio Durigan Junior <sergiodj@redhat.com>
Wed, 2 Sep 2015 04:46:43 +0000 (00:46 -0400)
committerSergio Durigan Junior <sergiodj@redhat.com>
Wed, 2 Sep 2015 04:46:43 +0000 (00:46 -0400)
commit73c6b4756a7cee53c274ed05fddcd079b8b7e57c
tree554b514730fc737939b3d9a6b279a48795046f06
parentad1c917a79e8c5aa67657f148415c1bee01b240f
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.
gdb/ChangeLog
gdb/solib-svr4.c