From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim blandy <jimb@redhat.com>, <gdb-patches@sources.redhat.com>
Subject: Re: macrotab.c -Werror
Date: Mon, 13 May 2002 17:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0205132025570.16238-100000@dberlin.org> (raw)
In-Reply-To: <3CE04DBC.9040100@cygnus.com>
On Mon, 13 May 2002, Andrew Cagney wrote:
> [second attempt at posting]
>
> Jim,
>
> FYI, I'm seeing:
>
> gdb/macrotab.c:504: warning: `best_depth' might be used uninitialized in
> this function
> gmake: *** [macrotab.o] Error 1
>
> for the code:
>
> /* It's not us. Try all our children, and return the lowest. */
> {
> struct macro_source_file *child;
> struct macro_source_file *best = 0;
> int best_depth;
>
> for (child = source->includes; child; child = child->next_included)
> {
> struct macro_source_file *result
> = macro_lookup_inclusion (child, name);
>
> if (result)
> {
> int result_depth = inclusion_depth (result);
>
> if (! best || result_depth < best_depth) <-- HERE
It's an obvious false positive (!best will be true the first time through,
meaning the only time we check best_depth, it's already been set at
least once).
Here, you can't just initialize best_depth to 0, you have to initialize it
to either INT_MAX, or inclusion_depth (result).
Sucks.
--Dan
next prev parent reply other threads:[~2002-05-14 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:35 Andrew Cagney
2002-05-13 17:28 ` Daniel Berlin [this message]
2002-05-14 12:55 ` Jim Blandy
2002-05-14 13:27 ` Andrew Cagney
2002-05-14 13:50 ` Daniel Berlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0205132025570.16238-100000@dberlin.org \
--to=dberlin@dberlin.org \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox