aboutsummaryrefslogtreecommitdiff
path: root/gdb/mdebugread.c
diff options
context:
space:
mode:
authorSergio Durigan Junior <sergiodj@redhat.com>2015-09-02 00:34:22 -0400
committerSergio Durigan Junior <sergiodj@redhat.com>2015-09-02 00:34:22 -0400
commitad1c917a79e8c5aa67657f148415c1bee01b240f (patch)
treede06969ae3fc8cefa74030df8570e2dce4432f6d /gdb/mdebugread.c
parent3bd7e5b7ee5ea0b3bbb4030ca841f66faad74f0f (diff)
downloadbinutils-ad1c917a79e8c5aa67657f148415c1bee01b240f.zip
binutils-ad1c917a79e8c5aa67657f148415c1bee01b240f.tar.gz
binutils-ad1c917a79e8c5aa67657f148415c1bee01b240f.tar.bz2
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 <sergiodj@redhat.com> * solib-svr4.c (svr4_handle_solib_event): Initialize 'val' as NULL
Diffstat (limited to 'gdb/mdebugread.c')
0 files changed, 0 insertions, 0 deletions