diff options
| author | Yao Qi <yao@codesourcery.com> | 2013-12-08 10:34:34 +0800 |
|---|---|---|
| committer | Yao Qi <yao@codesourcery.com> | 2013-12-08 10:34:34 +0800 |
| commit | e5e6f788e45ebdcf46c3a24f68994851186aa839 (patch) | |
| tree | 2ba98ae5022d719bc35abff9e70af5d835b085e4 /gdb/f-lang.h | |
| parent | 06fe43ca0ecf2cda7a7419bee2b5771d9d034f03 (diff) | |
| download | gdb-e5e6f788e45ebdcf46c3a24f68994851186aa839.zip gdb-e5e6f788e45ebdcf46c3a24f68994851186aa839.tar.gz gdb-e5e6f788e45ebdcf46c3a24f68994851186aa839.tar.bz2 | |
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.
Diffstat (limited to 'gdb/f-lang.h')
0 files changed, 0 insertions, 0 deletions