This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: win32-nat.c to windows-nat.c rename


 This problem has been fixed by the last patch from 
Christopher that changed the type of
cygwin_load_start and cygwin_load_end variables
from bfd_vma to CORE_ADDR type.

Thanks, Christopher !


Pierre Muller
Pascal language support maintainer for GDB



> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé?: Tuesday, January 13, 2009 11:23 AM
> À?: Pierre Muller
> Cc?: gdb-patches@sourceware.org
> Objet?: Re: win32-nat.c to windows-nat.c rename
> 
> > 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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]