Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.com>
To: Mike Stump <mikestump@comcast.net>, <gdb-patches@sourceware.org>
Subject: Re: simple typo with cache_ovly_table
Date: Wed, 21 Oct 2015 20:00:00 -0000	[thread overview]
Message-ID: <5627D2D5.4070607@ericsson.com> (raw)
In-Reply-To: <B2B5BD3D-8DF9-46EF-B3BF-4C2147528948@comcast.net>

On 15-10-21 01:51 PM, Mike Stump wrote:
> So our port causes a warning on failure of the types in question to be the same.  This fixes it.  Our CORE_ADDR is 64-bits, our ints are 32-bits.
> 
> Could someone shepherd it in?
> 
> 
> diff --git a/gdb/symfile.c b/gdb/symfile.c
> index f03fca7..e63a1c5 100644
> --- a/gdb/symfile.c
> +++ b/gdb/symfile.c
> @@ -3613,7 +3613,7 @@ simple_read_overlay_table (void)
>   cache_novlys = read_memory_integer (BMSYMBOL_VALUE_ADDRESS (novlys_msym),
> 				      4, byte_order);
>   cache_ovly_table
> -    = (unsigned int (*)[4]) xmalloc (cache_novlys * sizeof (*cache_ovly_table));
> +    = (CORE_ADDR (*)[4]) xmalloc (cache_novlys * sizeof (*cache_ovly_table));
>   cache_ovly_table_base = BMSYMBOL_VALUE_ADDRESS (ovly_table_msym);
>   read_target_long_array (cache_ovly_table_base,
>                           (CORE_ADDR *) cache_ovly_table,
> 

Hi Mike,

cache_ovly_table seems to be a

  unsigned (*cache_ovly_table)[4]

so why does it make sense to cast it to a

  CORE_ADDR (*)[4]

?

Simon


  reply	other threads:[~2015-10-21 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 19:47 Mike Stump
2015-10-21 20:00 ` Simon Marchi [this message]
2015-10-22  9:59   ` Mike Stump

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=5627D2D5.4070607@ericsson.com \
    --to=simon.marchi@ericsson.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mikestump@comcast.net \
    /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