Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA] mingw64: Skip over __main in main
Date: Mon, 27 Sep 2010 17:43:00 -0000	[thread overview]
Message-ID: <007f01cb5e60$971b6f20$c5524d60$@muller@ics-cnrs.unistra.fr> (raw)

  This patch enables recognition of call to __main
as part of the prologue of main for mingw64 binaries.

  It's almost a copy of the i386-tdep.c counterpart
(expect that I removed the 32-bit specific overflow code).

  It makes things more consistent with the way 32-bit binaries
are treated and allows to run testsuite on Cygwin
(after a few tricks ...).

  Is this patch OK?




2010-09-27  Pierre Muller  <muller@ics.u-strasbg.fr>

	* src/gdb/amd64-windows-tdep.c (amd64_skip_main_prologue): New function.
	(amd64_windows_init_abi): Register amd64_skip_main_prologue
	as gdbarch skip_main_prologue method.

Index: src/gdb/amd64-windows-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/amd64-windows-tdep.c,v
retrieving revision 1.6
diff -u -p -r1.6 amd64-windows-tdep.c
--- src/gdb/amd64-windows-tdep.c	29 Jan 2010 05:29:21 -0000	1.6
+++ src/gdb/amd64-windows-tdep.c	27 Sep 2010 16:15:28 -0000
@@ -122,6 +122,38 @@ amd64_windows_return_value (struct gdbar
     }
 }
 
+/* Check that the code pointed to by PC corresponds to a call to
+   __main, skip it if so.  Return PC otherwise.  */
+
+static CORE_ADDR
+amd64_skip_main_prologue (struct gdbarch *gdbarch, CORE_ADDR pc)
+{
+  enum bfd_endian byte_order = gdbarch_byte_order (gdbarch);
+  gdb_byte op;
+
+  target_read_memory (pc, &op, 1);
+  if (op == 0xe8)
+    {
+      gdb_byte buf[4];
+
+      if (target_read_memory (pc + 1, buf, sizeof buf) == 0)
+ 	{
+ 	  struct minimal_symbol *s;
+ 	  CORE_ADDR call_dest;
+
+	  call_dest = pc + 5 + extract_signed_integer (buf, 4, byte_order);
+ 	  s = lookup_minimal_symbol_by_pc (call_dest);
+ 	  if (s != NULL
+ 	      && SYMBOL_LINKAGE_NAME (s) != NULL
+ 	      && strcmp (SYMBOL_LINKAGE_NAME (s), "__main") == 0)
+ 	    pc += 5;
+ 	}
+    }
+
+  return pc;
+}
+
+
 static void
 amd64_windows_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
 {
@@ -140,6 +172,7 @@ amd64_windows_init_abi (struct gdbarch_i
   tdep->memory_args_by_pointer = 1;
   tdep->integer_param_regs_saved_in_caller_frame = 1;
   set_gdbarch_return_value (gdbarch, amd64_windows_return_value);
+  set_gdbarch_skip_main_prologue (gdbarch, amd64_skip_main_prologue);
 
   set_solib_ops (gdbarch, &solib_target_so_ops);
 }


             reply	other threads:[~2010-09-27 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27 17:43 Pierre Muller [this message]
2010-09-27 19:01 ` Mark Kettenis
2010-09-28  9:21   ` 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='007f01cb5e60$971b6f20$c5524d60$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.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