From: Joel Brobecker <brobecker@adacore.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: gdb-patches@sourceware.org
Subject: Re: win32-nat.c to windows-nat.c rename
Date: Tue, 13 Jan 2009 10:24:00 -0000 [thread overview]
Message-ID: <20090113102321.GX24105@adacore.com> (raw)
In-Reply-To: <003101c974b9$e05d4330$a117c990$@u-strasbg.fr>
> There is also a
> problem if trying to generate a mutibuild on cygwin on a 32 bit
> machine with --enable-64-bit-bfd:
Is that something new? Apart from moving some of the code to a different
file, I don't think I changed the actual code...
I'm wondering if I'm looking at the right version of the code.
For instance, it reports errors on the following two lines:
cygwin_load_start = (CORE_ADDR) (uintptr_t) ((char *) load_addr + 0x1000);
cygwin_load_end = cygwin_load_start + bfd_section_size (abfd, text);
> ../../purecvs/gdb/windows-nat.c:654: warning: cast from pointer to integer
> of different size
load_addr is an LPVOID (which is a void *), so casting it to (char *)
should be OK, then to (uintptr_t) should also be OK, and then to
a CORE_ADDR, it's an integer to integer conversion, that should be
OK too, no?
Do you see where the problem is? I'll see if I can reproduce
without cygwin...
--
Joel
next prev parent reply other threads:[~2009-01-13 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 9:09 [RFA/win32] move win32_xfer_shared_library to (new) win32-tdep Joel Brobecker
2009-01-10 16:51 ` Christopher Faylor
2009-01-11 4:19 ` Joel Brobecker
2009-01-11 4:24 ` Christopher Faylor
2009-01-11 6:29 ` Daniel Jacobowitz
2009-01-11 13:22 ` Joel Brobecker
2009-01-11 15:59 ` Jan Kratochvil
2009-01-11 18:37 ` Christopher Faylor
2009-01-12 1:11 ` Rename win32-* to windows-* Christopher Faylor
2009-01-12 19:42 ` Eli Zaretskii
2009-01-12 13:30 ` win32-nat.c to windows-nat.c rename Pierre Muller
2009-01-13 10:24 ` Joel Brobecker [this message]
2009-01-13 11:04 ` Pierre Muller
2009-01-13 17:55 ` Christopher Faylor
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=20090113102321.GX24105@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
/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