This is the mail archive of the
gdb-cvs@sourceware.org
mailing list for the GDB project.
gdb and binutils branch master updated. e5e6f788e45ebdcf46c3a24f68994851186aa839
- From: qiyao at sourceware dot org
- To: gdb-cvs at sourceware dot org
- Date: 8 Dec 2013 02:40:43 -0000
- Subject: gdb and binutils branch master updated. e5e6f788e45ebdcf46c3a24f68994851186aa839
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gdb and binutils".
The branch, master has been updated
via e5e6f788e45ebdcf46c3a24f68994851186aa839 (commit)
from 06fe43ca0ecf2cda7a7419bee2b5771d9d034f03 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e5e6f788e45ebdcf46c3a24f68994851186aa839
commit e5e6f788e45ebdcf46c3a24f68994851186aa839
Author: Yao Qi <yao@codesourcery.com>
Date: Sun Dec 8 10:34:34 2013 +0800
Avoid "may be used uninitialized" warning
Hi,
I see such warning below on one compiler I am using.
cc1: warnings being treated as errors
../../workspace/gdb/stack.c: In function 'frame_info':
../../workspace/gdb/stack.c:1519:20: error: 'caller_pc' may be used uninitialized in this function
Go through the gdb-patches archives and find the "canonical" way to
fix this warning is to initialize the variable.
gdb:
2013-12-08 Yao Qi <yao@codesourcery.com>
* stack.c (frame_info): Initialize variable caller_pc.
-----------------------------------------------------------------------
Summary of changes:
gdb/ChangeLog | 4 ++++
gdb/stack.c | 3 ++-
2 files changed, 6 insertions(+), 1 deletions(-)
hooks/post-receive
--
gdb and binutils