From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] gdbserver warnings
Date: Wed, 24 Apr 2002 07:22:00 -0000 [thread overview]
Message-ID: <20020424102213.A6310@nevyn.them.org> (raw)
In-Reply-To: <3CC69F25.3040704@suse.cz>
On Wed, Apr 24, 2002 at 02:03:49PM +0200, Michal Ludvig wrote:
> Hi,
> Now only two simple issues things in gdbserver to compile cleanly. First
> patch prevents:
> linux-low.c: In function `regsets_store_inferior_registers':
> linux-low.c:424: warning: cast from pointer to integer of different size
> on x86-64 where sizeof(void*) != sizeof(int). Why did you cast the last
> argument from pointer to integer? Manpage says it should be a void*...
> But I didn't test it on other archs...
Interesting. I got that from i386-linux-nat.c, IIRC:
if (ptrace (PTRACE_GETREGS, tid, 0, (int) ®s) < 0)
Might want to fix that one too.
> The second one prevents:
> regcache.h:26: warning: `struct inferior_info' declared inside parameter
> list
>
> 2002-04-24 Michal Ludvig <mludvig@suse.cz>
>
> * gdbserver/linux-low.c (regsets_fetch_inferior_registers),
> (regsets_store_inferior_registers): Removed cast to int from
> ptrace() calls.
This bit is OK.
> * gdbserver/regcache.h: Include server.h.
Sorry, I thought this warning had been introduced in my local copy, so
the fix was tied up with all my other patches... Please add
"struct inferior_info;" instead of "#include "server.h"". Approved
with that change.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2002-04-24 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 5:04 Michal Ludvig
2002-04-24 7:22 ` Daniel Jacobowitz [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=20020424102213.A6310@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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