From: Elena Zannoni <ezannoni@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: Elena Zannoni <ezannoni@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH/RFC] gag some compiler warnings
Date: Mon, 07 Jul 2003 18:35:00 -0000 [thread overview]
Message-ID: <16137.48900.330777.468485@localhost.redhat.com> (raw)
In-Reply-To: <86el17wd2k.fsf@elgar.kettenis.dyndns.org>
Mark Kettenis writes:
> Elena Zannoni <ezannoni@redhat.com> writes:
>
> > I am seeing these on a 64 bit system, when building gdb in 32-bit mode:
> >
> > /home/cygnus/ezannoni/gdb-6/src/gdb/infptrace.c: In function `child_xfer_memory':
> > /home/cygnus/ezannoni/gdb-6/src/gdb/infptrace.c:570: warning: cast to pointer from integer of different size
> >
> > The problem is that we pass a CORE_ADDR (which is 8 bytes long) to
> > ptrace and we cast it to PTRACE_ARG3_TYPE (which is 4 bytes long).
> >
> > Is this ok? Not too pretty, I know.
> > * infptrace.c (child_xfer_memory): Cast ptrace argument to long,
> > for cases in which CORE_ADDR size and pointer size don't agree.
>
> Hmm. I don't think this is OK. This could easily hide genuine
> problems. What system is this? Or perhaps a better question: what is
> the prototype of ptrace() in 32-bit mode on this system, and what is
> your definition of PTRACE_ARG3_TYPE on this system?
>
> Mark
This is a ppc64 system. But I think I have some local screw ups in the
way the machine is set up. PTRACE_ARG3_TYPE is void * (4 bytes) from
config/powerpc/nm-ppc64-linux.h while CORE_ADDR is 8 bytes.
Ignore this patch until I figure out what is really going on.
elena
prev parent reply other threads:[~2003-07-07 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 16:42 Elena Zannoni
2003-07-03 16:49 ` Richard Henderson
2003-07-03 20:49 ` Mark Kettenis
2003-07-07 18:35 ` Elena Zannoni [this message]
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=16137.48900.330777.468485@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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