Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Roland Schwingel <roland@onevision.com>
To: gdb-patches@sourceware.org, palves@redhat.com,
	       Joel Brobecker <brobecker@adacore.com>
Subject: [PATCH v4] Add dll trampoline code handling for windows 64bit
Date: Mon, 02 Apr 2012 14:54:00 -0000	[thread overview]
Message-ID: <4F79BD71.4010703@onevision.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hi,

Pedro Alves wrote on 30.03.2012 11:14:03:

 > Please send an updated patch, so we have in the archives the exact
 > patch as what is
 > checked in, and in case some other maintainer wants to take a look,
 > best have him look at
 > the refreshed patch.   In fact, if you had sent it already in that
 > email, there'd have been
 > no extra noise, right?  ;-)
Regarding the noise right. But not regarding generating additional work. 
But ok... Here is now generation 4 of my patch. It incorporates all 
formatting wishes of Joel.

I am still waiting for my copyright assignment stuff to be processed. It 
is now more than 2 weeks. What is the official way to ping it?

ChangeLog:

2012-04-02  Roland Schwingel <roland.schwingel@onevision.com>

          * amd64-windows-tdep.c: #include "frame.h".
          (amd64_windows_skip_trampoline_code): New function.
          (amd64_windows_init_abi): Add trampoline registration.

Thanks,

Roland

[-- Attachment #2: amd64-windows-tdep.c.patch --]
[-- Type: text/plain, Size: 2004 bytes --]

--- amd64-windows-tdep.c.orig	2012-03-02 01:06:12.000000000 +0100
+++ amd64-windows-tdep.c	2012-03-30 13:03:23.944573800 +0200
@@ -23,6 +23,7 @@
 #include "gdbtypes.h"
 #include "gdbcore.h"
 #include "regcache.h"
+#include "frame.h"
 
 /* The registers used to pass integer arguments during a function call.  */
 static int amd64_windows_dummy_call_integer_regs[] =
@@ -153,12 +154,49 @@
   return pc;
 }
 
+/* Check win64 DLL jmp trampolines and find jump destination.  */
+
+static CORE_ADDR
+amd64_windows_skip_trampoline_code (struct frame_info *frame, CORE_ADDR pc)
+{
+  CORE_ADDR destination = 0;
+  struct gdbarch *gdbarch = get_frame_arch (frame);
+  enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
+
+  /* Check for jmp *<offset>(%rip) (jump near, absolute indirect (/4)).  */
+  if (pc && read_memory_unsigned_integer (pc, 2, byte_order) == 0x25ff)
+    {
+      /* Get opcode offset and see if we can find a reference in our data.  */
+      ULONGEST offset =
+        read_memory_unsigned_integer (pc + 2, 4, byte_order);
+
+      /* Get address of function pointer at end of pc.  */
+      CORE_ADDR indirect_addr = pc + offset + 6;
+
+      struct minimal_symbol *indsym =
+        indirect_addr ? lookup_minimal_symbol_by_pc (indirect_addr) : NULL;
+      const char *symname = indsym ? SYMBOL_LINKAGE_NAME (indsym) : NULL;
+
+      if (symname)
+        {
+          if (strncmp (symname, "__imp_", 6) == 0
+              || strncmp (symname, "_imp_", 5) == 0)
+            destination =
+                read_memory_unsigned_integer (indirect_addr, 8, byte_order);
+        }
+    }
+
+  return destination;
+}
 
 static void
 amd64_windows_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
 {
   struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
 
+  /* Register trampoline handling code.  */
+  set_gdbarch_skip_trampoline_code (gdbarch, amd64_windows_skip_trampoline_code);
+
   amd64_init_abi (info, gdbarch);
 
   /* On Windows, "long"s are only 32bit.  */

             reply	other threads:[~2012-04-02 14:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-02 14:54 Roland Schwingel [this message]
2012-04-02 15:51 ` Pedro Alves
2012-07-25 17:57   ` Kai Tietz
2012-07-27 17:25     ` Pedro Alves
2012-07-30  6:57 Roland Schwingel

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=4F79BD71.4010703@onevision.com \
    --to=roland@onevision.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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