Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA v2] Allow cygwin native to compile with 	--enable-64-bit-bfd
Date: Thu, 29 Nov 2007 10:11:00 -0000	[thread overview]
Message-ID: <000901c83270$2a7f7060$7f7e5120$@u-strasbg.fr> (raw)
In-Reply-To: <20071125221238.GB10356@ednor.casa.cgf.cx>

> >> And the warning is?
> >
> >Cast from pointer to integer of different size.  Casts are the way
> >we've handled it elsewhere in GDB, but I wouldn't complain about a
> >wrapper; casting host pointers to CORE_ADDRs is an action we try to
> >keep to a minimum anyway.
> 
> I wouldn't mind a double cast either, if there is precedent for that.

 Here is a revised patch that only uses double typecasts.
 I ran the testsuite and got a slight improvement (2 FAIL less in
gdb.base/signals.exp),
but I doubt this is significant...

OK to check in?

ChangeLog entry:

2007-11-28  Pierre Muller  <muller@ics.u-strasbg.fr>

	*win32-nat.c: Allow compilation if CORE_ADDR is 8 byte long.
	Add "gdb_stdint.h" dependency required for uintptr_t type use.
	(handle_output_debug_string): Use uintptr_t typecast.
	(handle_exception): Ditto.
	(win32_xfer_memory): Ditto.

Index: gdb/win32-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/win32-nat.c,v
retrieving revision 1.140
diff -u -p -r1.140 win32-nat.c
--- gdb/win32-nat.c     24 Nov 2007 12:13:28 -0000      1.140
+++ gdb/win32-nat.c     28 Nov 2007 11:02:09 -0000
@@ -48,6 +48,7 @@
 #include "objfiles.h"
 #include "gdb_obstack.h"
 #include "gdb_string.h"
+#include "gdb_stdint.h"
 #include "gdbthread.h"
 #include "gdbcmd.h"
 #include <sys/param.h>
@@ -829,7 +830,8 @@ handle_output_debug_string (struct targe
   int retval = 0;

   if (!target_read_string
-    ((CORE_ADDR) current_event.u.DebugString.lpDebugStringData, &s, 1024,
0)
+       ((CORE_ADDR) (uintptr_t)
current_event.u.DebugString.lpDebugStringData,
+       &s, 1024, 0)
       || !s || !*s)
     /* nothing to do */;
   else if (strncmp (s, _CYGWIN_SIGNAL_STRING, sizeof
(_CYGWIN_SIGNAL_STRING) -
1) != 0)
@@ -1023,7 +1025,8 @@ handle_exception (struct target_waitstat
           and will be sent as a cygwin-specific-signal.  So, ignore SEGVs
if th
ey show up
           within the text segment of the DLL itself. */
        char *fn;
-       bfd_vma addr = (bfd_vma)
current_event.u.Exception.ExceptionRecord.Excep
tionAddress;
+       bfd_vma addr = (bfd_vma) (uintptr_t) current_event.u.Exception.
+
ExceptionRecord.ExceptionAddress;
        if ((!cygwin_exceptions && (addr >= cygwin_load_start && addr <
cygwin_l
oad_end))
            || (find_pc_partial_function (addr, &fn, NULL, NULL)
                && strncmp (fn, "KERNEL32!IsBad", strlen ("KERNEL32!IsBad"))
==
0))
@@ -1925,20 +1928,24 @@ win32_xfer_memory (CORE_ADDR memaddr, gd
                   struct target_ops *target)
 {
   DWORD done = 0;
+
   if (write)
     {
       DEBUG_MEM (("gdb: write target memory, %d bytes at 0x%08lx\n",
-                 len, (DWORD) memaddr));
-      if (!WriteProcessMemory (current_process_handle, (LPVOID) memaddr,
our,
+                 len, (DWORD) (uintptr_t) memaddr));
+      if (!WriteProcessMemory (current_process_handle,
+                              (LPVOID) (uintptr_t) memaddr, our,
                               len, &done))
        done = 0;
-      FlushInstructionCache (current_process_handle, (LPCVOID) memaddr,
len);
+      FlushInstructionCache (current_process_handle,
+                            (LPCVOID) (uintptr_t) memaddr, len);
     }
   else
     {
       DEBUG_MEM (("gdb: read target memory, %d bytes at 0x%08lx\n",
-                 len, (DWORD) memaddr));
-      if (!ReadProcessMemory (current_process_handle, (LPCVOID) memaddr,
our,
+                 len, (DWORD) (uintptr_t) memaddr));
+      if (!ReadProcessMemory (current_process_handle,
+                             (LPCVOID) (uintptr_t) memaddr, our,
                              len, &done))
        done = 0;
     }



  parent reply	other threads:[~2007-11-29 10:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-23  8:50 [RFC/RFA] " Pierre Muller
2007-11-24 21:07 ` Christopher Faylor
2007-11-24 22:47   ` Daniel Jacobowitz
2007-11-25 17:32     ` Christopher Faylor
2007-11-25 19:08       ` Daniel Jacobowitz
2007-11-25 22:12         ` Christopher Faylor
2007-11-26  9:12           ` Pierre Muller
2007-11-26 15:18             ` Ulrich Weigand
2007-11-29 10:11           ` Pierre Muller [this message]
2007-12-02  2:43             ` [RFA v2] " Christopher Faylor
2007-12-02  4:00               ` Daniel Jacobowitz
2007-12-03 15:18                 ` [RFA v3] " Pierre Muller
2007-12-06  9:23                   ` Christopher Faylor
2007-12-06 14:06                     ` Pierre Muller

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='000901c83270$2a7f7060$7f7e5120$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sourceware.org \
    /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