Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] target attributes [1/5] core and load from target function
Date: Wed, 29 Aug 2012 14:43:00 -0000	[thread overview]
Message-ID: <503E2A7A.2030709@codesourcery.com> (raw)
In-Reply-To: <503DCEC5.2010308@mentor.com>

On 08/29/2012 04:11 PM, Hui Zhu wrote:
> +static void
> +target_attribute_address_handler (struct gdb_xml_parser *parser,
> +				  const struct gdb_xml_element *element,
> +				  void *user_data,
> +				  VEC(gdb_xml_value_s) *attributes)
> +{
> +  int i, len;
> +  struct gdb_xml_value *attrs = VEC_address (gdb_xml_value_s, attributes);
> +  struct target_attribute *ta = *(struct target_attribute **)user_data;
> +  CORE_ADDR start, end;
> +  struct target_attribute_address *ta_addr;

I happen to see some compilation warnings on my new Fedora 16 box, while
these warnings don't appear on my Ubuntu box.

... -Werror -c -o target-memory.o -MT target-memory.o -MMD -MP -MF .deps/target-memory.Tpo ../../../git/gdb/target-memory.c
../../../git/gdb/target-attributes.c: In function ‘target_attribute_address_handler’:
../../../git/gdb/target-attributes.c:487:16: error: ‘end’ may be used uninitialized in this function [-Werror=uninitialized]
../../../git/gdb/target-attributes.c:486:18: error: ‘start’ may be used uninitialized in this function [-Werror=uninitialized]
../../../git/gdb/target-attributes.c: In function ‘target_attribute_attr_handler’:
../../../git/gdb/target-attributes.c:376:12: error: ‘type’ may be used uninitialized in this function [-Werror=uninitialized]
../../../git/gdb/target-attributes.c: In function ‘target_attribute_type’:
../../../git/gdb/target-attributes.c:632:3: error: ‘ret’ may be used uninitialized in this function [-Werror=uninitialized]
cc1: all warnings being treated as errors
make: *** [target-attributes.o] Error 1

The gcc I am using is 4.6.3
$ gcc --version
gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2)

We have to get these warnings fixed.

> +
> +  len = VEC_length (gdb_xml_value_s, attributes);
> +  for (i = 0; i < len; i++)
> +    {
> +      if (strcmp (attrs[i].name, "start") == 0)
> +        start = * (ULONGEST *) attrs[i].value;
> +      else if (strcmp (attrs[i].name, "end") == 0)
> +        end = * (ULONGEST *) attrs[i].value;
> +      else
> +        gdb_xml_error (parser, _("Unknown attribute name '%s'."),
> +		       attrs[i].name);
> +    }
> +
> +  ta_addr = xmalloc (sizeof (struct target_attribute_address));
> +  ta_addr->start = start;
> +  ta_addr->end = end;
> +
> +  ta_addr->prev = ta->addresses;
> +  ta->addresses = ta_addr;
> +}

-- 
Yao


  reply	other threads:[~2012-08-29 14:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  8:12 Hui Zhu
2012-08-29 14:43 ` Yao Qi [this message]
2012-09-02 10:39   ` Hui Zhu
2012-11-21  8:56     ` Hui Zhu
2012-11-30  6:03       ` Abid, Hafiz
2013-02-18 10:02         ` Hui Zhu
2013-02-18 11:45           ` Abid, Hafiz
2013-02-19 16:11             ` Hui Zhu
2013-02-26  3:34               ` Hui Zhu

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=503E2A7A.2030709@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hui_zhu@mentor.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