Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/ob]
Date: Tue, 11 Dec 2001 11:43:00 -0000	[thread overview]
Message-ID: <20011211144152.A22746@nevyn.them.org> (raw)
In-Reply-To: <3C164DDD.5020904@cygnus.com>

On Tue, Dec 11, 2001 at 10:18:05AM -0800, Andrew Cagney wrote:
> Just FYI,
> 
> I've checked the attached in as, er, obvious.  It fixes a
> -Wuninitialized warning.

I agree with the "er, obvious".

Would there be anything wrong with:

> *************** value_fn_field (value_ptr *arg1p, struct
> *** 971,983 ****
>     struct minimal_symbol *msym;

adding = NULL to the line above?

>   
>     sym = lookup_symbol (physname, 0, VAR_NAMESPACE, 0, NULL);
> !   if (!sym)
>       {
>         msym = lookup_minimal_symbol (physname, NULL, NULL);
>       }
> - 
> -   if (!sym && !msym)
> -     return NULL;
>   
>     v = allocate_value (ftype);
>     if (sym)
> --- 972,988 ----
>     struct minimal_symbol *msym;
>   
>     sym = lookup_symbol (physname, 0, VAR_NAMESPACE, 0, NULL);
> !   if (sym != NULL)
>       {
> +       msym = NULL;
> +     }
> +   else
> +     {
> +       gdb_assert (sym == NULL);

This assert in particular bugs me.  Adding asserts that the compiler
can obviously eliminate, since sym isn't volatile...


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-12-11 19:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-11 10:18 [patch/ob] Andrew Cagney
2001-12-11 11:43 ` Daniel Jacobowitz [this message]
2001-12-11 18:40   ` [patch/ob] Andrew Cagney

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=20011211144152.A22746@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.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